Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.2.X
Votes
0
Found in
2020.2
2020.2.0b8
2021.1
Issue ID
1293607
Regression
No
ProfilerRecorder API to record "GC Allocated In Frame" reports 0 bytes if the Profiler Window isn't currently recording
How to reproduce:
1. Open the user's attached project("AngryBots2.zip")
2. Window>Analysis>Profiler
3. Press record in the Profiler
4. Enter Play mode
5. Notice "GC Allocated In Frame Memory" shows that there is memory allocated in the Game View
6. Stop recording in the Profiler
Expected results: "GC Allocated In Frame Memory" still shows memory allocated
Actual results: "GC Allocated In Frame Memory" shows 0 bytes allocated
Reproducible with: 2020.2.0b14, 2021.1.0a8
Couldn't test with: 2018.4.30f1, 2019.4.16f1, 2020.1.16f1 (Couldn't upgrade/downgrade)
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
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
- Crash on invalid_parameter_internal when starting Standalone Profiler
Resolution Note (fix version 2021.1):
Fixed in Unity 2021.2.0a1 and above
Resolution Note (fix version 2021.1):
Fixed in Unity 2021.1.0b3 and above
Resolution Note (fix version 2020.2):
Fixed in Unity 2020.2.3f1 and above