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
- Sprite Shape Corners and Edges are invisible when a closed Sprite Shape is used
- Script icon Gizmos cause lag/performance issues in Scene view even when the Scene Camera is not pointed at Gizmos
- Visual artifacts when the normal map is using mipmap and Bilinear filtering or Point filtering in URP Lit shader
- Crash on MonoBehaviour::VirtualRedirectTransfer when closing Editor after removing HDPR and importing Water Samples before
- Scene from a specific project is stuck loading in the Web Player with the "Uncaught (in promise) TypeError" error thrown in the browser console
Add comment