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
- Crash in StackAllocator::TryDeallocate when calling ParticleSystemRenderer.BakeMesh
- Modifying scoped registries in project manifest does not update Package Manager UI window
- Models change their position in scene when reimporting them in 2019.4
- Texture 'Read/Write' option does not double the memory in Profiler
- [Particle System] Ribbon trails are connected in the wrong order when moving the Particle System with faster movements
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