Search Issue Tracker
Fixed
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
- ScrollView clips content when under an ancestor that has a filter set
- "Retrieving array element that was out of bounds" error thrown when attempting to remove a column from a Multi-Column List View
- Multi-Column List View horizontal scroll resets to left most position when scrolling vertically
- Floating License is lost for concurrent jobs
- Warning "Failed to insert item" is logged when Assigning Project to Organization's Project in the Project Settings
Resolution Note:
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.