Search Issue Tracker
Fixed
Fixed in 2021.3.X, 2021.3.5f1
Votes
0
Found in
2021.3.0f1
Issue ID
UUM-1807
Regression
No
[Backport] UI Components cause GC Allocation when enabled
Reproduction steps:
1. Open users attached project
2. Select File/Build and Run
3. Select Window/Analysis/Profiler and set Player as a target
4. In the Overview, search for GameObject.SetActive() and observe the GC Alloc
Expected result: 0 bytes of "GC Alloc"
Actual result: 60.3KB of "GC Alloc"
Reproducible with: 2019.4.17f1, 2020.1.17f1, 2020.2.1f1, 2021.1.0b1
Could not test with: 2018.4.29f1(could not downgrade)
Notes:
1. 2019.4.17f1 - 2020.2.0a5 (30.2KB GC allocation)
2. 2020.2.0a7 - 2021.1.0b1 (60.3KB GC allocation)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Animator Controller Layer name stays unchanged in Layers tab when renamed from Inspector
- [RenderingDebugger]Motion vectors are displayed when Phong Tessellation is used on the material and Skinned Motion Vectors are enabled on the GameObject's Skinned Mesh Renderer component
- Shader Graph Enum Keywords always select last element in Entries when Stages is set to Fragment and Recursive Rendering is enabled in the Scene
- [Mac] Glitchy visual artifacts appear when moving around a scene with Sphere Handles
- Crash on memcpy_repmovs when selecting NavMesh Agent objects while in Play Mode in a specific scene
Resolution Note (fix version 2021.3):
Fixed in 2021.3.5f1