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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Add comment