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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment