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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
MatasVa
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
Unity3d-025
Oct 12, 2019 00:56
Same scenerio as MIHKELT. Issue is still here, happening when calling LoadAssetAsync with addressables
MihkelT
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
Shawn-Halwes
Sep 04, 2019 17:59
Getting this on only one computer on v2017.4.31f1 was this fixed in 2017.4 LTS?
trialforce
Mar 09, 2019 00:34
Happens to me too!
heridan
Mar 07, 2019 11:25
Please fix it in 2017LTS
pginiotis
Mar 03, 2019 14:19
The issue is already fixed in 2018.3.8f1, which should arrive soon-ish.
stastic
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 ?
Flokami
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)
ManuBuriedAtSea
Feb 15, 2019 14:20
Not fixed! Casting Shadows From Sprites still brings up this Error!