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
- 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