Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0a6
2018.1.0f1
Issue ID
1031233
Regression
Yes
[OSX] GUIView::EndCurrentContext(bool) crash using this.Close(); on custom EditorWindow
To reproduce:
1. Open users attached project "NitroDubz.zip"
2. Make sure not to press anywhere in the editor
3. Press Tools > NitroDubz
4. Repeat step 2 4 - 6 times
Expected result: Unity does not crash
Actual result: Unity crashes after 4 - 6 times
Reproduced on: 2018.1.0a6 2018.1.0b1 2018.1.0f2 2018.2.0b3 2018.3.0a1
Not reproduced: 2017.3.2f1 2017.4.3f1 2018.1.0a1
Notes:
Usually crashes on the first couple of times pressing Tools > NitroDubz
MacOS High Siera 10.13.4, 10.13.3 also
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment