Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.1.0a11
2019.2
2019.2.15f1
2019.3
2020.1
Issue ID
1206727
Regression
No
TempBuffer <RenderTexture> is not released in memory when using deprecated Realtime Global Illumination
How to reproduce:
1. Open the attached project's Scene labeled "TestScene"
2. Open the Memory Profiler (Window->Analysis->Memory Profiler)
3. Capture Editor's Memory Snapshot
4. Enter the Play Mode
5. Exit the Play Mode after ~5 seconds
6. Capture Editor's Memory Snapshot
7. Repeat the 4-6 steps for a few times (3-4)
8. Inspect the captured Memory Snapshots
Expected result: Every Snapshot should have a similar count of "TempBuffer <RenderTexture>"
Actual result: There is an increasing number of "TempBuffer <RenderTexture>" when entering and then leaving the Play Mode
Reproducible with: 2019.1.0a11, 2019.2.17f1, 2019.3.0f4, 2020.1.0a18
Not reproducible with: 2018.4.15f1, 2019.1.0a10
Couldn't test with: 2017.4.36f1 (Package Manager does not exist)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.2):
Fixed in Unity 2020.2.0a3
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b13.3980 (Memory Profiler 0.2.4-preview.1)
Resolution Note (fix version 2019.4):
Fixed in Unity 2019.4.30f1