Search Unity

Windows player crash (stack overflow in garabage collection?)

Discussion in 'Windows' started by Tallek, Jul 3, 2019.

  1. Tallek

    Tallek

    Joined:
    Apr 21, 2014
    Posts:
    34
    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:
     
    Lipoly likes this.
  2. joncham

    joncham

    Unity Technologies

    Joined:
    Dec 1, 2011
    Posts:
    276
  3. Tallek

    Tallek

    Joined:
    Apr 21, 2014
    Posts:
    34