Search Issue Tracker
By Design
Votes
1
Found in
2020.1.0a16
2020.2.0a13
Issue ID
1252836
Regression
Yes
Sprites reference both the original Sprite assets and Sprite Atlas resulting in increased memory usage
Steps to reproduce:
1. Play the attached "TestFor1071494.zip" project's SampleScene
2. In the Profiler window go to Memory view in Detailed mode
3. Click Take Sample: Editor
4. In the batch viewer go to Assets -> Texture2D
5. Notice the entries for both the Sprite Atlas and each individual Sprite asset
Expected result: Sprites only reference the Sprite Atlas
Actual result: Sprites reference the Sprite Atlas and the original Sprite assets
Reproducible with: 2020.2.0a14, 2020.1.0b11, 2020.1.0a16
Not Reproducible with: 2020.1.0a15
Environment: Win and Mac
Same bug was reported for 2018.3 : https://fogbugz.unity3d.com/f/cases/1071494/
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
- [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
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (2020.1.X):
In Editor both Original texture and Atlas texture are held as references by SpriteFrame. Hence the info shown by Profiler. When building Player/AssetBundles ONLY the Atlas texture is referenced and serialized. Hence you see the additional texture as reference in playmode.