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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note (fix version 2019.2):
This crash does not reproduce when using the new scripting runtime. Please target .NET 4.x Equivalent.