Search Issue Tracker
Fix In Review
Fix In Review for 6000.3.13f1, 6000.4.1f1, 6000.5.0b2, 6000.6.0a2
Under Consideration for 6000.0.X
Votes
0
Found in
6000.0.71f1
6000.3.12f1
6000.4.1f1
6000.5.0b1
6000.6.0a1
Issue ID
UUM-137789
Regression
No
RenderTarget memory usage is cumulative and is creating a memory leak when changing Scenes
How to reproduce:
1. Open the attached “IN-130634.zip” Project
2. Open the Memory Profiler (Window → Analysis → Memory Profiler)
3. Open the “a” Scene from the Scenes Folder
4. Enter Play Mode
5. In the Memory Profiler select Capture
6. In the Game View press the “Button” multitple times
7. Re-focus the Memory Profiler and press Capture
8. Observe Memory Usage
Actual result: RenderTexture memory usage is cumulative with each Scene Switch
Expected result: RenderTexture memory usage is culled after Scene Switch
Reproducible with: 6000.0.71f1, 6000.3.12f1, 6000.4.1f1, 6000.5.0b1, 6000.6.0a1
Reproducible on: macOS M3 Pro 26.3.1
Not reproducible on: No other environment tested
Note: Multiple captures might be require to see the spikes as occasionally the RenderTexture is not update and memory usage doesn’t rise or lower
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in 6000.6.0a2
Resolution Note (fix version 6000.6.0a2):
Fixed in 6000.6.0a2
Resolution Note (fix version 6000.5.0b2):
Fixed in 6000.5.0b2
Resolution Note (fix version 6000.4.1f1):
Fixed in 6000.4.1f1
Resolution Note (fix version 6000.3.13f1):
Fixed in 6000.3.13f1