Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0f2
Issue ID
1066038
Regression
No
[MacOS] Crash on project load when custom mono envs are exported via launchctl
How to reproduce:
1. Open a terminal
2. Write into terminal "launchctl setenv MONO_DEBUG disable_omit_f"
3. Open Unity
4. Create a new project
5. Observe CPU Monitor Activity
Expected results: The project created without problems
Actual results: Unity stuck at not responding
Reproduces: 2017.1.5f1, 2017.2.3f1, 2017.4.9f1, 2018.1.9f1, 2018.2.4f1, 2018.3.0a8
Note: unsetting the environment variable fixes the issue "launchctl unsetenv MONO_DEBUG disable_omit_fp"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Non-standard error icon is used in Shader Graph
- GameObject drops to the last position in the Hierarchy when a RectTransform Component is added
- 'NullReferenceException' error is thrown when the Tutorials window is closed and the "Welcome Dialog" is pressed
- Mouse Postion can become max value or infinity when using touch input with Legacy Input Module
- Crash on RaiseException when creating a multiplayer room while toggling UI
Add comment