Search Issue Tracker
Fixed in 2022.1.X
Votes
5
Found in
2019.4
2020.1
2020.2
2021.1
2021.1.0a9
Issue ID
1299752
Regression
No
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)
Comments (1)
-
Peter77
Dec 30, 2020 20:36
Related forum thread:
https://forum.unity.com/threads/unity-2021-1-performance-overview.993186/#post-6626896
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
- Resources.UnloadUnusedAssets() freezes the Editor when releasing Mesh objects
- 16-bit Sprite Textures have a banding effect and loss of data when packing into Variant Sprite Atlas
- HDRP Cluster artifacts when having more than 100 lights
- ParticleCollisionEvent.intersection generates extremely high values when particles collide while in Play Mode
- Custom attributes are not properly converted to subgraphs
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a3