Search Issue Tracker
Fixed in 2018.2
Fixed in 2017.2, 2017.4, 2018.1
Votes
0
Found in
2017.3.1f1
Issue ID
1006814
Regression
Yes
SpriteRenderer leaks memory when changing sliced sprite's size
Steps to reproduce:
1. Download 1006814_repro.zip and open "test" scene
2. Enter play mode
3. Open Profiler window
4. Select Memory and set to Detailed
5. Expand Scene Memory
6. Every few seconds press button "Take Sample: Editor"
Expected results: SpriteRenderer's memory usage doesn't change
Actual results: SpriteRenderer's memory usage increases 2-3 KB per second
Note: In Sprite Renderer draw mode must be set to Sliced.
Reproduced with: 2018.2.0a2, 2018.1.0b9, 2017.3.1p2, 2017.2.2f1, 2017.1.3p2, 2017.1.2p3
Not reproducible with: 5.6.5p2
Regression introduced in: 2017.1.2p3
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
- [Performance Regression] AnimatorEditorTests Rebind Big Hierarchy 341 Transform
- [Performance Regression] LogTests DebugLogWarning has regressed in performance
- [Performance Regression] ClassListSelector_AddNewElements has regressed in performance
- [Performance Regression] UIElementsStyling: ClassListSelector_AddNewElements test has regressed
- [Performance Regression] UIElementsStyling NameSelector_AddNewElements has regressed from 18.4
hanklord
Sep 18, 2018 07:41
Still have the memory leak problem when setting SpriteRenderer draw mode to sliced with changing Width & Height or changing the Sprite
Reproduced with: 2017.4.10f1