Search Issue Tracker
By Design
Votes
3
Found in
2017.4.0f1
2018.2.14f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1105050
Regression
No
Atlased sprite is never unloaded from editor memory after exiting Play Mode
How to reproduce:
1. Open user-submitted project (asset_database_test)
2. Enter Play Mode
3. Click the 'Load atlased' button
4. Exit Play Mode
5. Open the Profiler window
6. In the detailed Memory Profiler take a sample of the Editor
7. Navigate to Assets > Texture2D
Expected result: Texture2D does not contain the atlased sprite since the Play Mode has been exited
Actual result: Texture2D contains the atlasted sprite
Reproducible with: 2017.4.21f1, 2018.3.7f1, 2019.1.0b4, 2019.2.0a4
Could not test with: 2019.2.0a5, 2019.2.0a6
Notes:
EditorUtility.UnloadUnusedAssetsImmediate and Resources.UnloadUnusedAssets() do not unload the texture from the Editor memory
Restarting the Editor unloads the Texture from the Editor memory as expected
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (2019.3.X):
By design, they are not unloaded.
The SpriteAtlases in project held by SpriteAtlasDatabase are held in memory but the unused Textures are unloaded.
Note: This is only in the case of Editor. In Runtime, SpriteAtlasDatabase does not exist.