Search Issue Tracker
Fixed in 3.0.0-pre.1
Votes
1
Found in [Package]
2.2.0-preview.4
Issue ID
1246924
Regression
No
GC.Alloc allocates 40 bytes in RenderPipelineManager.DoRenderLoop_Internal() method when Unity Recorder package is installed
How to reproduce:
1. Create a new project with URP or HDRP template
2. Import the Unity Recorder package from the Package Manager
3. Make sure to close the Profiler window if it was already opened and reopen it again (Window -> Analysis -> Profiler)
4. Enter Play Mode
5. Select any frame recorded in the Profiler window
Expected result: GC.Alloc in PlayerLoop -> RenderPipelineManager.DoRenderLoop_Internal() is equal to 0 bytes
Actual result: GC.Alloc is equal to 40 bytes in every single frame (even when not using Unity Recorder in any way)
Reproducible with: 2.0.0-preview.6 (2019.4.4f1), 2.1.0-preview.1 (2020.1.0b16), 2.2.0-preview.4 (2020.2.0a18)
Could not test with: 2018.4.25f1 (GC.Alloc is already equal to 2.4 kilobytes without the Recorder package and it's unclear whether the 40 bytes are added to it when it's installed)
Notes:
The issue doesn't occur when creating a project without URP/ HDRP template and importing the package through the Package Manager
Comments (1)
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
evapro
Mar 29, 2022 12:03
Reproducible with 2019.4.17 LTS 2DRenderer