Search Issue Tracker
Third Party Issue
Votes
0
Found in
2019.4
2019.4.21f1
2020.3
2021.1
2021.2
Issue ID
1318755
Regression
Yes
[macOS] Unity crashes when exception thrown after a DLL has been loaded
Repro steps:
1. Download and open project from the link below
2. Open scene "LipSync_Demo"
3. Enter Play Mode
4. Exit and Enter Play Mode a second time if it doesn't crash on first
Expected: Editor doesn't crash
Actual: Editor crashes
Reproducible with: 2019.4.26f1, 2020.3.7f1, 2021.1.6f1, 2021.2.0a17
Not reproducible with: 2018.4.34f1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (2021.2.X):
The crash is due to the oculus lipsync plugin using it's own crash handling that is preempting mono's own. This results in access violations via null references manifesting as hard crashes instead of being re-thrown as a managed NullReferenceException. Provided the user mono's workaround for this issue: https://www.mono-project.com/docs/advanced/signals/