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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment