Search Issue Tracker

Fixed in 2018.3

Fixed in 2018.3, 2019.1



Found in



Issue ID




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

Graphics - General


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
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 ===========

Update: fixed in 2019.2.0a6, 2019.1.0b5 and 2018.3.8f1

Comments (42)

  1. Efe79f65b219936f2d04856fe29b09ac?d=mm


    Apr 16, 2019 13:03

    Keep your mind sharp and enrich your vocabulary with this addicting and challenging word puzzle game that’s keeping everyone hooked. Download it now on PC for free. Read more for tips, tricks, and the complete game review.

  2. 61e800df75b1d6f86d08536d73a8afec?d=mm


    Mar 16, 2019 12:26

    I also face this error during java program excutation, when i run my code it shows so i really suffers a lot due to this error i want a proper solution to resolve this error as soon as possible.

  3. 61e2cf0463cbe68f11b20add43fd9202?d=mm


    Mar 09, 2019 00:34

    Happens to me too!

  4. A5dff54a95e6daed737f719ed345b039?d=mm


    Mar 07, 2019 11:25

    Please fix it in 2017LTS

  5. 005bf585e366831e2d2fec7bf4120206?d=mm


    Mar 03, 2019 14:19

    The issue is already fixed in 2018.3.8f1, which should arrive soon-ish.

  6. F3354d65a42868c9440739f2165c5802?d=mm


    Feb 19, 2019 17:46

    Saw that there were some SpriteRenderer and JobTempAlloc memory leak fix in 2018.3.4. I gave that version a try and still having the crash, just this time it doesn't spew out graphics errors in the console log anymore.

    Will this fix be coming to 2018 ?

  7. D4dea88794bd79277f177652935675d6?d=mm


    Feb 17, 2019 20:08

    Roses are red,
    Violets are blue,
    My unity is crashing,
    and nothing to do.

    (This error maybe linked with some access violation error in builds that I have only with this kind of setup)

  8. 0be1b593c886369acf6216c6030782d8?d=mm


    Feb 15, 2019 14:20

    Not fixed! Casting Shadows From Sprites still brings up this Error!

  9. 3f02570b109622d0914978ce7f678dbb?d=mm


    Feb 15, 2019 12:40

    NOT RESOLVED! Our game uses cast shadows everywhere and deadlines are approaching, need fix ASAP!

  10. A5dff54a95e6daed737f719ed345b039?d=mm


    Feb 14, 2019 07:46

    same issue in 2017.4.19f1

All about bugs

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