Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.1.18f1
Issue ID
UUM-56051
Regression
No
Editor freezes when DualSense controller is connected and disconnected repeatedly
Reproduction steps:
1. Open the attached “MacOSControllerFreeze.zip“ project
2. Enter Play mode
3. Connect the DualSense controller via cord and wait until the name of the controller is shown in the Game window
4. Disconnect the controller
5. Repeat 3-4 steps for 5-20 times
Expected result: Controller is detected and the Editor doesn’t freeze
Actual result: Controller is no longer detected and the Editor freezes
Reproducible with: 2023.1.18f1
Reproduced on: macOS Darwin 14.0 (M1)
Notes:
- The issue was not reproducible by CQA
- User noted that once the HID controller thread is frozen, a call to IOHIDManagerSetDeviceMatchingMultiple will result in the call blocking forever. This affects Rewired because Unity's Input System is crashing, and if Rewired is initialized at any point afterward (even in a different Play session in the editor), the application will freeze forever
- User also noted that sometimes macOS completely crashes and restarts itself upon connecting and disconnecting the controller
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
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.