Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
0
Found in
2017.1.5f1
2017.4.34f1
2018.1.9f2
2018.2.21f1
2018.4.13f1
2019.1.14f1
2019.2.18f1
2019.3.0f6
2020.1.0a19
2020.1.0a20
Issue ID
1212015
Regression
No
[Physics] Using huge numbers of vertex for Polygon/Edge collider causes stack overflow.
Steps to repro:
1. Open attached project
2. Hierarchy > 2D Object > Sprite
3. Inspector > Add component > Polygon Collider 2D
4. Inspector > Polygon Collider 2D > Points > Paths > Size
5. Enter a high value more than 10000 for 'Size'
Actual Result:
Editor crashes on entering values much more than 10,000.
Expected Result:
Editor may freeze whilst it processes large numbers of vertex (etc) but it should not crash.
Note:
The attached video shows 20 million paths being added which produces 20 million 5 vertex shapes so 10 million shapes. The Editor will stop responding (freeze) because it's doing a lot of work and will likely take many hours and possibly days to process that.
Reproducible in:
2020.1.0a19, 2019.3.0f6, 2018.4.13f1, 2017.4.34f1, 2017.1.5f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment