Search Issue Tracker
Fixed in 4.0.3
Votes
0
Found in [Package]
3.0.8
Issue ID
1220091
Regression
No
[2D SpriteShape] SpriteShapeController leaks memory when zero control points are used
How to reproduce:
1. Open the "SampleScene" Scene in the attached "SpriteShape-Reproducer.zip" Unity project
2. Select the "SELECT THIS" GameObject in the Hierarchy
3. Observe the Console window
Expected result: a Sprite Shape Controller without any control points does not cause Console errors
Actual result: Console errors "A Native Collection has not been disposed, resulting in a memory leak. Enable Full StackTraces to get more details." and "ArgumentException: GetControlPoint accessed with invalid Index 0 / 0" are printed
Reproducible with: 2D SpriteShape 3.0.1 (Unity 2019.3.0a11), 4.0.1 (Unity 2020.1.0a25)
Could not test with: 2D SpriteShape versions 2.1.0-preview.11 and older due to Package errors
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
- [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
Resolution Note (fix version 4.0.3):
Fixed in 2D Sprite Shape 4.0.3