Search Issue Tracker
Fixed
Votes
0
Found in
2019.2.0a3
2019.2.10f1
2019.3
2020.1
Issue ID
1194942
Regression
Yes
StackOverflowException error is thrown when K-D Tree is generated
How to reproduce:
1. Open attached project ("StackSize.zip")
2. Open SampleScene scene
3. Enter Play mode
4. Exit Play mode
5. Build and Run project
Expected result: No StackOverflowException is thrown
Actual result: StackOverflowException is thrown in the Scene but not in Build
Reproducible with: 2019.2.12f1, 2019.3.0b10, 2020.1.0a12
Not reproducible with: 2017.4.34f1, 2019.1.0a1 (Error in MONO Scene and Build, IL2CPP works without errors), 2019.2.0a2 (Error in MONO Scene and Build, IL2CPP only in Scene)
Note: Error is thrown in both IL2CPP and MONO scripting backends
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
The code raises a StackOverflowException with a call stack 1000 levels deep. We do use operating system defaults for thread stacks. It is unlikely we will increase the main thread stack space. I would suggest using a non-recursive algorithm or doing the calculation on a non-main thread where you create it with a large enough stack space.