Search Issue Tracker
Fixed in 2020.1
Fixed in 2017.4
Votes
0
Found in
2017.4.16f1
2017.4.31f1
2018.3.0b7
2019.2.0a5
Issue ID
1181825
Regression
Yes
Editor crashes after throwing "GetGfxDevice() should only be called from main thread" errors
How to reproduce:
1. Open the project, provided in the EnvIromen VM ("Editor Crash Unity Project")
2. Enter Playmode
Expected result: errors are not thrown and the editor doesn't crash
Actual result: errors are not thrown and editor eventually crashes
Reproducible with: 2017.4.16f1, 2017.4.34f1, 2018.3.0b7, 2018.3.7f1, 2019.2.0a1, 2019.2.0a5
Not reproducible with: 2017.4.15f1, 2018.3.0b6, 2019.3, 2020.1
Note:
- The crash is not reproducible on every device
- The occurs does not reproduce consistently
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
- [Windows] The Unity import progress is not shown in the Windows taskbar
- Custom shader creation APIs are missing the AssetImportContext and thus can't handle includes correctly
- 2019.4: PackedMemorySnapshot: nativeObjects.gcHandleIndex contains -1 always
- [Hub] Project "Remove from list" option is behind notifications when selecting the most bottom project in the list
- [Android][Vulkan] Black Screen renders on devices with Adreno 640 and Mali GPU's
Resolution Note (fix version 2020.1):
Fixed in: 2018.3.8f1, 2019.2.0a6