Search Issue Tracker
Won't Fix
Votes
2
Found in
2017.3.0f3
Issue ID
1000791
Regression
No
Unused assets are not unloaded when opening a different scene
Steps to reproduce:
1. Open “AssetMemory.zip” Unity project
2. Open “Example” scene
3. Select “ReferenceHolder” object in Hierarchy
4. Set “Release Managed References On Destroy” value to True in Inspector
5. Open Window->Profiler
6. Make sure that Memory Profiler is added and Detailed mode is enabled in Profiler
7. Click "Take Sample: Editor" in Profiler
-Notice the “Cat” sprite reference under Assets->Sprite in Profiler
8. File->New Scene
9. Click "Take Sample: Editor" in Profiler
-Notice the “Cat” sprite reference under Assets->Sprite in Profiler still remains after changing the scene
Expected results:
Asset is unloaded after opening a new scene scenes
Actual results:
Asset is not unloaded after opening a new scene scenes
Reproduced in: 2018.2.0a1, 2018.1.0b7, 2017.3.1p1, 2017.2.1p4, 2017.1.3p1, 2017.1.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment