Search Issue Tracker
Third Party Issue
Votes
0
Found in
2019.4.7f1
2020.2.0a17
2020.3
2021.1
2021.2
Issue ID
1327649
Regression
Yes
[macOS] Native OSX OpenGLCore crash when OpenGL Context for a window is set
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Enter the Play Mode
3. Wait for the Scene to load
Expected result: Scene is loaded
Actual result: Unity Editor hangs/freezes
Reproducible with: 2020.2.0a17, 2020.3.7f1, 2021.1.6f1, 2021.2.0a16
Not reproducible with: 2018.4.34f1, 2019.4.25f1, 2020.1.17f1, 2020.2.0a16
Note:
- With Unity 2021.2.0a16 Editor crashes when exiting Play Mode instead
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
- [VFX Graph/Oculus/Vulkan] Line Output is not visible on Oculus
- [VFX/Oculus/GLES 3] Screen Space particles are flipped on Y
- Colors majorly change when the Volume Component's "Weight" property value changes from 0 to any small value
- [VFX/Oculus/GLES 3] Skinned Mesh and Mesh sampling effects do not appear when TexCoord is used
- Serializable type loses its "NaN" value when copying and pasting it in the Inspector window
Resolution Note (2021.2.X):
This issue is caused by a changes made by Apple in the MacOS Catalina (11.0) SDK that restricts certain context methods that can be called in multi-threaded situations. In particular, the crash results from calling the context methods in a thread supporting a native OpenGL plugin (i.e., a custom .dylib not provided by Unity).
Running the Editor with `-force-gfx-direct` resolves these crashes and can be used as a temporary workaround.
The issue can be mitigated by updating native plugin implementations to avoid calling these context methods from a thread other than the main thread.