Description

While active and ticking, the built-in FS_MasterField actor instance continuously creates several new components every frame, which are never cleaned up until the actor is destroyed. This can happen indefinitely if the field has its "Activation Type" set to "OnTick" or "OnTickWithDelay". It can also happen during a period of time after the initial configured "Delay" and before the confiured "Lifespan" elapses. With default settings, more than 1000 components can be created per second.

The problem can be detected by enabling "LogBlueprintComponentInstanceCalls 1" and "log LogBlueprint Log" on the console, which makes the Output Log become spammed with blueprint actor component instance creation messages. It can also be detected by using the "TEDS debugger" in UE 5.7 and later, in which the created components appear with "ActorComponentTypeTag" and label "NODE_*". Examples:

NODE_AddCullingField

NODE_AddOperatorField

NODE_AddRadialFalloff

NODE_AddNoiseField

NODE_AddRandomVector

NODE_AddUniformScalar

NODE_AddUniformVector

Inspecting the blueprint code while in PIE shows that nodes like "Add Culling Field", "Add Radial Falloff" and "Add Operator Field" (all of which create new components on the actor) are called continuously every frame. There is no cleanup code for those components.

It has been reported that, in the Editor, this also causes the GameThread to slow down steadily over time, because these ever-growing components are processed by the Mass Entity Editor Subsystem.

Steps to Reproduce

Tested on all versions from UE 5.3 to latest source.

1. Create a new level from the Basic template

2. Add an "FS_MasterField" actor to the level (from /Engine/EditorResources/FieldNodes)

3. On the Details panel for the "FS_MasterField" instance:

3.1. Set "Activation Type" to "OnTick"

4. PIE

Issue detection using logs:

1. Console: LogBlueprintComponentInstanceCalls 1

2. Console: log LogBlueprint Log

3. Watch as the output log is spammed with component creation calls

Issue detection using the TEDS debugger:

1. Make sure that plugin "TEDS: Editor Data Storage Features" is enabled

2. Open the "TEDS Debugger" (Tools Menu – Debug – TEDS Debugger)

3. Click on the Plus icon on the far right of the "Select" row, select "TypedElementLabelColumn" from the dropdown

4. Click on the plus icon on the far right of the "All" row, select "ActorComponentTypeTag" from the dropdown

5. Watch as the "Element Count" on the bottom of the window quickly grows and the table is spammed with field components labeled "NODE_*" that get created and never destroyed

Using Lifespan:

1. On the Details panel for the "FS_MasterField" instance:

1.1. Set "Activation Type" to "Delay"

1.2. Set "Use Lifespan" tp true

1.3. Set "Field Lifespan" to 2.0

2. PIE

2.1. Using one of the detection methods above, note that components are created continuously after "Delay" and before "Lifespan" elapses.

Have Comments or More Details?

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

0
Login to Vote

Unresolved
ComponentUE - Simulation - Visual
Affects Versions5.35.8
CreatedMar 25, 2026
UpdatedMay 1, 2026
View Jira Issue