Search Issue Tracker
Fixed in 9.0.0-preview.27
Votes
1
Found in [Package]
8.0.1
Issue ID
1226448
Regression
No
[2D Renderer] Using more than one camera that renders out to a Render Texture creates GC Alloc every frame
How to reproduce:
1. Open attached project "Universal Camera Garbage.zip" and scene "SampleScene"
2. Enter Play mode
3. Open Window -> Analysis -> Profiler
4. In Profiler search write "RenderPipelineManager"
5. Observe the GC Alloc for both processes
Expected result: no Garbage Collector allocations are made
Actual result: every frame 40B+ garbage allocations are made
Reproducible with: 2019.3.9f1 (7.1.8, 7.3.1), 2020.1.0b5, 2020.2.0a7 (8.0.1)
Could not test with: 2017.4, 2018.4 (2d renderer was not yet implemented)
Comments (2)
-
Personuo
Feb 16, 2021 16:38
Never fixed.
I am using unity 2020.2.4, and urp 10, this problem is still here -
DomeCreator
Jul 22, 2020 15:17
Facing the exact same issue with HDRP
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 9.0.0-preview.27):
Verified in:
Version: 2020.2.0a17
Package: Universal RP 9.0.0-preview.35
Resolution Note (fix version 9.0.0-preview.27):
Verified in:
Version 2019.4.5f1 Universal RP 7.4.1