Search Issue Tracker

Active

Votes

26

Found in

2018.3.0f2

Issue ID

1110007

Regression

Yes

Editor throws "GetGfxDevice() should only be called from main thread" errors and eventually crashes when in Play Mode

Graphics - General

-

-

Priority: 2Necessary for shipping a final release

-

Severity: 1Crash, freeze, data loss, work stops

How to reproduce:
1. Open attached project "Breeze"
2. Enter Play Mode
3. Play the game for 2minutes
------------
Observe errors "GetGfxDevice() should only be called from main thread" spammed in the Console
-OR-
Observe the crash following the errors

Reproduced with: 2018.3.0b7, 2018.3.1f1, 2019.1.0a13
Does not reproduce with: 2018.3.0b6

Note: For 2019.1 Entering Play Mode is not needed to receive same error in Console

========== OUTPUTTING STACK TRACE ==================

0x000000014034D99D (Unity) SharedObject<SharedMeshData,1,SharedObjectDeleteReleaseOp<SharedMeshData> >::Release
0x0000000142203ADA (Unity) GfxDeviceWorker::RunCommand
0x000000014220B2CB (Unity) GfxDeviceWorker::RunExt
0x000000014220B3C4 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x0000000140A6F094 (Unity) Thread::RunThreadWrapper
0x00007FFE0B3A1FE4 (KERNEL32) BaseThreadInitThunk
0x00007FFE0DF2CB81 (ntdll) RtlUserThreadStart

========== END OF STACKTRACE ===========

Comments (16)

  1. C1adff0f832dacc30d1fbc9dc838e276?d=mm

    rrazcueta

    Jan 20, 2019 03:15

    I got this error again with Unity 2017.4.18f1 as well

  2. C1adff0f832dacc30d1fbc9dc838e276?d=mm

    rrazcueta

    Jan 20, 2019 03:13

    I got this error again with Unity 2017.4.18f1 as well

  3. C1adff0f832dacc30d1fbc9dc838e276?d=mm

    rrazcueta

    Jan 20, 2019 03:13

    I got this error again with Unity 2017.4.18f1 as well

  4. C1adff0f832dacc30d1fbc9dc838e276?d=mm

    rrazcueta

    Jan 20, 2019 03:13

    I got this error again with Unity 2017.4.18f1 as well

  5. E3d5bdcc92db2f4e7e3a02076ba77837?d=mm

    Lavapotion

    Jan 18, 2019 10:29

    Were having the exact same issue on 2018.3.0f2. Casting shadows from sprites seems to be the issue. Anyone got a workaround for this?

  6. 6d8c02bfc2ccac4ca5e25fde797639aa?d=mm

    Thompson11

    Jan 15, 2019 17:19

    We narrowed it down to casting (not receiving) shadows from our sprite renderers.

  7. 6d8c02bfc2ccac4ca5e25fde797639aa?d=mm

    Thompson11

    Jan 15, 2019 17:19

    We narrowed it down to casting (not receiving) shadows from our sprite renderers.

  8. 6d8c02bfc2ccac4ca5e25fde797639aa?d=mm

    Thompson11

    Jan 15, 2019 17:17

    We narrowed it down to casting (not receiving) shadows from our sprite renderers.

  9. 5ef56af45eebaf25ff5959b31f7be4aa?d=mm

    Scott_T

    Jan 14, 2019 07:13

    Same issue. Editor keeps crashing. Would like to see this fixed.

  10. 5ef56af45eebaf25ff5959b31f7be4aa?d=mm

    Scott_T

    Jan 14, 2019 07:02

    Same issue. Editor keeps crashing. Would like to see this fixed.

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.