Windows player crash (stack overflow in garabage collection?)

Unity Engine
,
1

We are having an issue with our 64-bit Windows player crashing with no information in the log file and no crash dump information. I attached Visual Studio to the process prior to the crash an I was able to capture the following stack trace and exception, but the initial frames of the stack appear to be lost. I don’t know what I am looking at, but it kinda appears like it is a stack overflow in the garbage collection process that is causing the crash.

The game was built with Unity 2018.3.8f1

Exception captured by Visual Studio:
Exception thrown at 0x00007FFAEEAC3EF8 (mono-2.0-bdwgc.dll) in Game.exe: 0xC0000005: Access violation writing location 0x00000089BF4C0000. occurred

Call stack captured by Visual Studio:

1 Like
2

This bug will likely be fixed by Unity Issue Tracker - Editor silent crash when attempting to load a new Scene after allocating data

Generally due to large arrays (or collections based on arrays) leading to a stackoverflow during processing.

3

Thanks for the reply and the information! I’ll try upgrading to 2018.4 once that fix is released.