Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2019.1.X
Votes
37
Found in
2018.3.0b7
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
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 ===========
--------------------------------------
Update: fixed in 2019.2.0a6, 2019.1.0b5 and 2018.3.8f1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
rrazcueta
Jan 20, 2019 03:13
I got this error again with Unity 2017.4.18f1 as well
rrazcueta
Jan 20, 2019 03:13
I got this error again with Unity 2017.4.18f1 as well
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?
Thompson11
Jan 15, 2019 17:19
We narrowed it down to casting (not receiving) shadows from our sprite renderers.
Thompson11
Jan 15, 2019 17:19
We narrowed it down to casting (not receiving) shadows from our sprite renderers.
Thompson11
Jan 15, 2019 17:17
We narrowed it down to casting (not receiving) shadows from our sprite renderers.
Scott_T
Jan 14, 2019 07:13
Same issue. Editor keeps crashing. Would like to see this fixed.
Scott_T
Jan 14, 2019 07:02
Same issue. Editor keeps crashing. Would like to see this fixed.
validname1
Jan 13, 2019 11:07
Need this fixed ASAP. It is slowing progress on my game.... gonna have to revert versions until this is resolved. *Sigh*
Camera doesn't matter. It also happens on perspective. More details here: https://forum.unity.com/threads/case-1110540-getgfxdevice-should-only-be-called-from-main-thread.600064/
rrazcueta
Jan 11, 2019 22:59
Posting to say I've been having this issue as well. I'm using an orthographic camera and shadow enabled sprites, and I'm not sure if those are causing the issues.