Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2019.1.X
Votes
0
Found in
2017.3.0a1
2018.1.0a1
2018.2.0a1
2018.2.16f1
2018.3.0a1
2019.1.0a1
Issue ID
1103205
Regression
No
Allocating too many variables in a method leads to a crash
Steps to reproduce:
1. Download and open the attached project
2. Add LoadMegaCrash.cs to a a gameobject
3. Enter playmode
Expected result: warning about too many allocations
Actual result: hard crash
Reproduced on 2017.3.0a1, 2017.4.16f1, 2018.1.9f2, 2018.2.17f1, 2018.3.0b11, 2019.1.0a10
Fixed 2019.2.0a7
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (fix version 2019.2):
This crash does not reproduce when using the new scripting runtime. Please target .NET 4.x Equivalent.