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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
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.