Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2017.4.X
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
- Incorrect Burst Exception Control Flow in Editor due to Mono Handling of calli instruction
- [Linux] Packman options to add package from Git URL doesn't always show the window directly below the + button
- "UnityEngine.SystemInfo.processorFrequency" logs a value of 0 on M1 macs
- Editor redirects to a broken page when pressing question mark "?" in the Inspector window
- Editor directs to non-existent page when pressing "Learn more..." for Asset Pipeline
Resolution Note (fix version 2020.1):
Fixed in: 2018.3.8f1, 2019.2.0a6