Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.29f1
2022.3.11f1
2023.3.0a8
Issue ID
UUM-50991
Regression
No
Sprite Atlas remains loaded in memory after scene change or unloading assets
Sprite Atlas remains loaded in memory after scene change or unloading assets
Repro steps:
* In attached project, open SampleScene and enter Playmode, use Frame Debugger to observe sprites in scene referencing atlas textures
* Using Memory profiler capture, observe atlas Texture2D reference in memory
* Press 'Space' to open empty scene, press '1' to unload all unused assets or '2' to unload all atlases
* Using Memory profiler capture, observe atlas Texture2D reference is still in memory
Expected results: Sprite atlas and atlased textures should not be in memory after switching scene or being unloaded
Actual results: Sprite atlas and atlased textures remain in memory after switching scene or being unloaded
Test platforms: Windows 11
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
- ComputeShader compilation is executed sequentially, resulting in subpar performance
- Crash on UnityObjectToString(Object*) when an object has a field with a type mismatch and an active Animator
- Visual Effect Graph Node creation folder colors are not set to default by default
- The Attach button is active and shows the Attached to Visual Effect" tooltip when the Visual Effect Graph is no longer attached
- The same subgraph window can be opened multiple times after a domain reload
Resolution Note:
In playmode, it is expected to have Texture2D and SpriteAtlas references in memory even if they are referenced in other scenes
Outside playmode, SpriteAtlas references in memory are expected but in itself consumes very little memory (a few properties and references) usually in KBs. The editor's memory profiler might show larger memory used due to the Editor window itself and other editor objects that use extra memory