40 B of GC Alloc is created when CheckDistanceCondition runs in a Behavior Graph

Package: Unity Behavior

Won't Fix

1.0.X

Thank you for reporting a bug to Unity. We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available. Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

How to reproduce:
1. Open the attached "IN-139656_BehaviorPackageBugs.zip" project
2. Open the "SampleScene"
3. Enter Play mode
4. Go to Window -> Analysis -> Profiler
5. Make sure the profiler is recording
6. Wait for a few seconds
7. Click on the CPU module graph
8. Observe the Profiler Hierarchy

Actual result: GC Alloc on PlayerLoop shows 40 B
Expected result: GC Alloc on PlayerLoop is 0

Reproducible with: 1.0.5 (6000.0.16f1), 1.0.15 (6000.3.13f1)

Reproducible on: Windows 11
Not reproducible on: No other environments tested

Note: GC Alloc in version 1.0.5 is 100 B

40 B of GC Alloc is created when CheckDistanceCondition runs in a Behavior Graph

Package: Unity Behavior

Won't Fix

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

40 B of GC Alloc is created when CheckDistanceCondition runs in a Behavior Graph

Package: Unity Behavior

Statuses

Won't Fix

Resolution Notes

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?