Search Issue Tracker
Duplicate
Votes
0
Found in
2017.3.0a1
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1117663
Regression
No
[.NET 4.x] Editor and mono Player crash with Stack overflow exception due to nested methods calls
Steps to reproduce:
1. Download the attached project and open "InitailScene" scene
2. Make sure that Scripting Runtime is set to .NET 4.x
3. Enter play mode
4. Click next scene
Expected results: Editor loads a new scene
Actual results: Editor crashes with no stack trace
Reproduced with: 2019.2.0a1, 2019.1.0a14, 2018.3.3f1, 2017.4.18f1
Not reproducible with: .NET 3.5 Scripting Runtime and IL2CPP player with both .NET 4.x and .NET 3.5
Comments (1)
-
r3eckon
Mar 07, 2019 22:15
I'm having a very similar problem with a recursive algorithm crashing the editor. Happens only on .NET 4.x runtime while using 3.5 works perfectly.
Log shows a StackOverflowException is the cause, but using logging I found out that the function causing issues only loops about 34 times before the editor crashes, which is not even close to looking like an infinite loop. It's like the stack becomes tiny when using 4.x.
Temporary workaround is to use .NET 3.5 but since it'll be removed in Unity 2019 that's not going to last.
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
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [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
This is a duplicate of issue #1098168