Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.3.0f2
Issue ID
1117354
Regression
No
[MacOS] Crash at pthread_mutex_lock when turning off JoyCon controller having used JoyconLib plugin
To reproduce:
1. Open users attached project "JoyconLibCrashBug.zip"
2. Connect JoyCons to iMac with Bluetooth observe as the little lights on the JoyCons are bouncing around
3. Enter Play mode. If JoyCons are connected, moving JoyCons should move the blue cubes in the Editor
4. Exit Play mode and unfocus the Editor (press on a finder window or everywhere else)
5. Press the little Sync button on the JoyCons near the little lights to turn JoyCons off
Expected result: the controllers are disconnected and Unity doesn't crash
Actual result: Unity crashes at pthread_mutex_lock
Reproduced on:
2017.4.0f1 2017.4.22f1 2018.3.8f1 2019.1.0b6 2019.2.0a7
Notes:
Doesn't reproduced on Win 10 machines.
Reproduces on MacOS machines.
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- Long Sprite names are not truncated in the Inspector window name label and the preview labels when a Sprite with a long name is selected
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
Resolution Note (2020.1.X):
We were able to reproduce this internally using the sample project at https://github.com/Looking-Glass/JoyconLib. This is not a Unity issue. The crash is occurring in that project because HIDapi.hid_exit() is never called to free the library. This should be done in OnApplicationQuit() in the instance of this sample.