Search Issue Tracker
By Design
Votes
0
Found in
6000.3.0a6
6000.4.0a1
Issue ID
UUM-115963
Regression
No
RTHandles remain allocated when unloading a scene that uses a custom renderer feature
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/StartScene.unity“ Scene
3. Enter the Play Mode
4. Open the Memory Profiler (Window > Analysis > Memory Profiler)
5. Click the “Capture New Snapshot“ button in the Memory Profiler window
6. In the Game View, click the “Load sample scene” button
7. Open the Memory Profiler again and click the “Capture New Snapshot” button
8. In the Game View, click the “Load Start Scene” button
9. Open the Memory Profiler again and click the “Capture New Snapshot”
10. Compare the first and third memory snapshots by navigating to the Unity Objects tab in the Memory Profiler and checking the RenderTexture allocation values
Expected result: The third memory snapshot should match the first memory snapshot
Actual result: The third memory snapshot still shows RenderTexture allocations remaining in memory
Reproducible with: 1.1.8 (6000.0.56f1 , 6000.2.2f1, 6000.3.0a6)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
Unity will render the last captured frame if there is no camera in a scene