Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0f3
Issue ID
983476
Regression
No
Memory leaking when executing SpriteAtlas.GetSprite()
To reproduce:
1. Open user's project
2. Enter Play mode
3. Observe memory usage in Profiler or Windows Task Manager
Expected: memory is not leaking
Actual: memory is leaking
Reproduced in: 2017.1.3f1, 2017.2.1p1, 2017.3.0p1, 2018.1.0b1
Note: a script is toggling rendered sprite between 16 Sprite Atlas sprites each frame
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment