Search Issue Tracker
Fixed
Fixed in 7000.0.0
Votes
0
Found in [Package]
1.7.0
Issue ID
ISXB-658
Regression
No
Silent crash when Stadia controller is reconnected via cord while Device Debug View State window is opened
Reproduction steps:
1. Open the attached “StadiaCrash.zip“ project
2. Connect the Stadia controller via cord
3. Open the Input Debugger window (Window > Analysis > Input Debugger)
4. Double-click on the “Google Inc. Stadia Controller” to open Device Debug View
5. Click on the “State”, “Display Raw Memory” and “Bits/Hew” buttons in this exact order
6. Disconnect and reconnect the controller via the cord
7. Observe the Editor
Expected result: Editor doesn’t crash
Actual result: Editor crashes
Reproducible with: 1.7.0 (2022.3.10f1)
Reproduced on: macOS Ventura 13.3.1 (Intel), Windows 10
Not reproduced on: No other environment tested
Notes:
- Reproduction on macOS Ventura 13.3.1 (Intel) is inconsistent
- Confirming without properly testing as per request of the developers
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
- Default Preset application and Reset() method execution order is different when adding a Component via the Inspector versus calling Reset via the Component context menu
- Scene view is not outputting HDR when the "Use HDR Display Output" option is enabled, DX12 is selected as the Graphics API, and URP/HDRP is in use
- Sprite Atlas results in suboptimal packing even when "Allow Rotation" is enabled
- References placed in a UnityEvent change to the same reference when multi-selecting their GameObjects
- "ShadowCaster2D" Component doesn't work when the "Casting Source" is set to "Polygon Collider 2D"
Resolution Note (fix version 7000.0.0):
Fixed an editor crash caused by input debugger device state window reusing cached state when reconnecting Stadia controller.
Resolution Note:
Input state window is now force-closed when the device it is inspecting is disconnected.