Search Issue Tracker
Fixed
Fixed in 6000.3.0b10, 6000.4.0a4
Votes
0
Found in
6000.0.59f1
6000.2.7f1
6000.3.0b4
6000.4.0a1
Issue ID
UUM-121201
Regression
Yes
GC.Alloc is called by ProbeVolume.OnDrawGizmos() when playing
How to reproduce:
- Create a new 3D HDRP Sample project
- Enable Gizmos in the Game view (on the top right)
- Open the Window → Analysis → Profiler window
- Enable Deep Profiling and Call Stacks
- Enter Play Mode
- Search for “GC.Alloc“ in the CPU Usage Hierarchy and select any one of the results
- To the right of the Profiler Hierarchy, change "No Details" to "Calls"
- Observe the 'Called From' section on the right on the Profiler
Expected result: No calls to GC.Alloc are made from ProbeVolumes.OnDrawGizmos()
Actual result: GC.Alloc is called from ProbeVolumes.OnDrawGizmos()
Reproducible in: 2023.1.0a1, 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Could not test in: 2022.2.0a18
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- ProbeVolume.OnDrawGizmos() Allocate ~96 B each frame
- Could not reproduce on a project that was created in 2023.1.0a1
- Only reproduces if Gizmos are enabled
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Multiple "[...] is inaccessible due to its protection level" errors are thrown when opening project with Unity Version Control installed
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Sorting icons are tiny and misaligned in Import Activity window
- The Undo system does not record HideFlags.HideInHierarchy changes
Add comment