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
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
- Flickering bright white dots in the Scene when the Android Platform is selected and DX11 Graphics API is used with Iris(R) Xe Graphics GPU
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
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.