Search Issue Tracker
Duplicate
Votes
0
Found in
2020.3.48f1
2021.3.25f1
2022.2.19f1
2023.1.0b16
2023.2.0a14
Issue ID
UUM-35815
Regression
No
GC.Collect causes spikes in the CPU when an additional camera uses a RenderTexture
Reproduction steps:
1. Open attached project "RenderTextureBug.zip"
2. Open Assets > Scenes > SampleScene
3. Open Windows > Analysis > Profiler
4. Enter Play mode and observe Profiler
Expected result: Stable performance
Actual result: Spikes in performance caused by GC.Collect
Reproduced with: 2020.3.48f1, 2021.3.25f1, 2022.2.19f1, 2023.1.0b16, 2023.2.0a14
Reproducible on: Windows 10
-
Resolution Note:
We have validated the repro project with the UUM-40249 fix and confirmed the issue is no longer reproducible.
Based on our testing result, we close this case as duplicate.Quote from UUM-40249 fix resolution:
"Fixed runtime performance drops when multiple views that uses incompatible RTHandle descriptors are rendered within a frame."
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-40249
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
This is a duplicate of issue #UUM-19089