Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.4
2019.1
2019.1.10f1
2019.2
2019.3
2020.1
Issue ID
1170061
Regression
No
Memory leak in Scene Memory/RenderTexture when Scene View is active and 'Animated Materials' + 'Post Processings' toggles are on
How to reproduce:
1. Download the tester-attached archive(SSMS.zip)
2. Create a new Unity project
3. Import the SSMS folder
4. Reset the Editor layout to Default
5. Enable Animated Materials and Post Processings for Scene View
6. Drag SSMS/SSMSGlobalFog.cs onto the Main Camera
7. Drag SSMS/SSMS.cs onto the Main Camera
8. Open the Window > Analysis Profile
9. Switch to Editor profiling mode and select the Memory module
Expected result: textures count and their allocated memory do not increase
Actual result: textures count and their allocated memory keep increasing
Reproducible with: 2018.3.0a6, 2018.4.15f1, 2019.2.18f1, 2019.3.0f5, 2020.1.0a19
Could not test with: 2017.4.30f1, 2018.3.0a5 (Script that is causing the issue is incompatible)
Notes:
Reproduces only when Scene View is active
Reproduces only when 'Animated Materials' and 'Post Processings' are toggled on for the Scene View
Switching to Game View and back to Scene View stops this memory allocation, reloading the scene makes it start happening again
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:
Every few months we look at bugs which we have not had the opportunity to fix yet. We try to be as diligent as we can and want to prioritize bugs that are causing issues with shipping and frequent pain points in day to day works. To ensure we are targeting the most important bugs we regularly close out older bugs that have not reached this threshold over the past months. The bug you have currently raised has not met this threshold for fixing over the last few months.