Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.2.X, 2017.4.X, 2018.1.X
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
- PrntScreen (Snapshot) key is not working on UWP on both old and new input systems
- Show compiled code for compute shaders has the "Cancel" button greyed out
- Realtime direct lighting is missing on dynamic objects under when using Shadowmask or Subtractive lighting mode(s)
- [Device Simulator] When simulator window is narrow, toolbar controls deform and some become inacessible
- Black albedo when using Enlighten Realtime GI in HDRP Player
shubhamswaraj2021
Aug 18, 2020 16:02
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
litopesiao
Apr 13, 2020 13:59
I am trying to animate a sliced sprite's height size. Where am I going wrong with my code?
I can transform Game Objects easily enough (<a href="https://topshadesailsgoldcoast.com/">residential shade sails</a>, position, scale etc), but applying the same steps doesn't seem to work for the Sprite Renderer component.
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