Description

When using the ConstructorHelpers templated function, FObjectFinder, with Niagara assets, the editor crashes.

 

Tested in 4.21.2 (CL - 4753647), 4.22 (CL  - 5660361),  4.23 (CL - 5806860)

Steps to Reproduce
  1. Create a Blank C++ project
  2. Enable the Niagara plugin
  3. Create a Radial Burst Niagara System called NewNiagaraSystem
  4. Create a C++ AActor derived class named MyActor
  5. Navigate to the MyActor source file
  6. Within the AMyActor constructor enter the following: 
FObjectFinder (LoadObject/StaticLoadObject/FSoftObjectPath.TryLoad), e.g. ConstructorHelpers::FObjectFinder<UNiagaraSystem>Var(TEXT("NiagaraSystem'/Game/NewNiagaraSystem.NewNiagaraSystem'"));
  1. Compile and Run the project from the IDE
  2. Create an Blueprint from the MyActor class

Expected: An instance of NewNiagaraSystem is loaded

Result: The editor crashes

Callstack

LoginId:f0847e0641d1167c58b18ead90c0bf20 EpicAccountId: Unhandled exception UE4Editor_CoreUObject UE4Editor_Niagara UE4Editor_CoreUObject UE4Editor_CoreUObject UE4Editor_CoreUObject UE4Editor_CoreUObject UE4Editor_CoreUObject UE4Editor_CoreUObject UE4Editor_CoreUObject UE4Editor_CoreUObject UE4Editor_MyProject!ConstructorHelpersInternal::FindOrLoadObject<UNiagaraSystem>() [c:\program files\epic games\ue_4.22\engine\source\runtime\coreuobject\public\uobject\constructorhelpers.h:36] UE4Editor_MyProject!AMyActor::AMyActor() [c:\test\myproject\source\myproject\myactor.cpp:12] UE4Editor_CoreUObject UE4Editor_CoreUObject UE4Editor_CoreUObject UE4Editor_CoreUObject UE4Editor_Core UE4Editor_Core UE4Editor_Projects UE4Editor_Projects UE4Editor UE4Editor UE4Editor UE4Editor UE4Editor UE4Editor kernel32 ntdll

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-72592 in the post.

34
Login to Vote

Fixed
ComponentUE - Niagara
Affects Versions4.224.234.21.2
Target Fix4.24
Fix Commit9967127
Main Commit10001516
Release Commit9967127
CreatedApr 10, 2019
ResolvedNov 5, 2019
UpdatedNov 13, 2019
View Jira Issue