Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.1.0a3
2018.2.5f1
Issue ID
1073880
Regression
Yes
[MAC] Unity crashes when pressing CMD + Q in Non-Matching Editor Installation window
How to reproduce:
1. Open a project in Non-Matching Editor Installation (For example a 2018.1 project in 2018.2 Editor)
2. When "Opening Project in Non-Matching Editor Installation" window pops up, press Command + Q
Expected result: Editor quits without crashing
Actual result: Editor quits with a crash
Reproduced in: 2018.1.0a3, 2018.1.0b1 ,2018.1.9f2, 2018.2.6f1, 2018.3.0a10
Not reproducible in: 2017.1.5f1, 2017.2.3p4, 2017.4.10f1, 2018.1.0a1, 2018.1.0.a2 (Editor does not react to Command + Q)
Note1: Using Alt+ F4 on Windows 10 does not cause Unity to crash
Note2: Only reproduces on MacOSX version: 10.10 and lower. (Reproduced in 10.9.4, 10.10.2, Not reproducible in 10.11.2, 10.12.6, 10.13.6)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment