Search Issue Tracker
Fixed in 10.1.0
Votes
1
Found in [Package]
9.0.0-preview.14
Issue ID
1259717
Regression
No
[URP] ScriptableRenderContext.GetCamera -> Array.Resize creates garbage every frame when more than one camera is active
How to reproduce:
1. Create new Universal RP template project
2. Create multiple cameras
3. Open Editor -> Window -> Analysis -> Profiler
4. In Profiler, enable Deep Profile
5. Enter Play mode
6. In Profiler, press on the graph and in search for "ScriptableRenderContext.GetCamera()"
7. Observe allocated garbage
Expected result: no garbage is created
Actual result: depending on the amount of cameras in the scene, the garbage is created
Reproducible with: 2019.4.2f1 (7.3.1, 7.4.1), 2020.1.0b14, 2020.2.0a16 (8.1.0, 9.0.0-prev.14)
Not reproducible with: 2018.4.24f1 (LWRP 4.10.0-preview)
Comments (1)
-
Justin15620
Jul 21, 2021 06:52
Hello, may I know if this fix will be backported to 7.4.1 or other versions supported by 2019.4 LTS?
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
- Value defaults to an unsupported unit when entering a large enough number in a Style's Float Variable in UI Builder
- Hub restarts without prompting the user if he really wants to do so when there's an Installation in progress if the user has already canceled the restart once
- Open in Sprite Editor Button Label goes out of bounds when UI Builder's Inspector is resized to it's smallest size
- Light Explorer Intensity field accepts NaN value for 2D Lights while Inspector Intensity field doesn’t
- Sprite Atlas is not selected right after creation in the Inspector when Sprite Atlas V2 is enabled
Resolution Note (fix version 10.1.0):
Fixed in 2021.1.0a1