Search Issue Tracker

Fixed in 2018.3.X

Fixed in 2019.1.X



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 (44)

  1. Aced5dd27efb0a216dc4eb128e140de5?d=mm


    Jan 02, 2021 22:57

    Still reproducible with: 2019.4.16f1 (e05b6e02d63e)

    0x00007FF77A59EF83 (Unity) GfxDeviceWorker::RunCommand
    0x00007FF77A5AAE2C (Unity) GfxDeviceWorker::RunExt
    0x00007FF77A5AB218 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
    0x00007FF77B479063 (Unity) Thread::RunThreadWrapper
    0x00007FF831107C24 (KERNEL32) BaseThreadInitThunk
    0x00007FF8312ED4D1 (ntdll) RtlUserThreadStart

  2. 75dbb2ea6509b3bcda9dd217eb6ef504?d=mm


    Oct 12, 2019 00:56

    Same scenerio as MIHKELT. Issue is still here, happening when calling LoadAssetAsync with addressables

  3. 4fe414b95ee8a6de6aa10cc41e1f5fcc?d=mm


    Oct 03, 2019 06:21

    Got this error on 2019.1.11f today! It is NOT completely fixed most obviously because otherwise i would not have got this error. Can't upvote this issue because it is MARKED fix but it is not actually fixed. Perhaps there are improvements towards the fix but not completely fixed as it still happens in 2019.1.11f this day

  4. F2bbba4266abb4a5cf79f0e4228b2a2f?d=mm


    Sep 04, 2019 17:59

    Getting this on only one computer on v2017.4.31f1 was this fixed in 2017.4 LTS?

  5. 61e2cf0463cbe68f11b20add43fd9202?d=mm


    Mar 09, 2019 00:34

    Happens to me too!

  6. A5dff54a95e6daed737f719ed345b039?d=mm


    Mar 07, 2019 11:25

    Please fix it in 2017LTS

  7. 005bf585e366831e2d2fec7bf4120206?d=mm


    Mar 03, 2019 14:19

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

  8. 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 ?

  9. 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)

  10. 0be1b593c886369acf6216c6030782d8?d=mm


    Feb 15, 2019 14:20

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

Add comment

Log in to post comment

All about bugs

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