Search Issue Tracker
In Progress
Fixed in 1.12.0
Fix In Review for 7000.0.0
Votes
1
Found in [Package]
1.11.2
Issue ID
ISXB-1258
Regression
Yes
[Input System] The Editor freezes when pressing 'A' on the controller and using touch input at the same time
Reproduction steps:
1. Open the “IN-89900” project
2. Open the “SampleScene” scene
3. Connect the controller
4. Go to the Simulator view
5. Enter Play Mode
6. Press the button in the middle of the screen with a mouse and a controller’s 'A' button at the same time
7. Observe the Editor
Expected result: The button is pressed
Actual result: The Editor freezes and never recovers
Reproducible with: 1.11.2 (2021.3.45f1, 2022.3.54f1, 6000.0.30f1, 6000.1.0a7)
Not reproducible with: 1.10.0, 1.11.1 (2022.3.54f1)
Testing environment: Windows 11 Pro
Not reproduced on: Windows Standalone (does not simulate touch input)
Notes:
- Also reproducible with Nintendo Switch Player (by user)
- Sometimes the Controller is not required (it freezes when pressing the button with mouse)
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
- [sw-unity-6-1] Scene view renders any light differently when more than one camera exists and neither have the "MainCamera" tag
- Project tab navigates to the previous folder when undoing (CTRL+Z) GameObject placement in the Scene
- Blue lines appear on the sides of the "Fit Canvas" or "Fit viewport" button when it's clicked in the UI Builder.
- PlayableDirector's state remains set to Playing even when the timeline's time property exceeds its duration.
- Favorites section does not collapse in the Project window when holding the ALT key
Resolution Note (fix version 7000.0.0):
Removal of pointers was assumed to always succeed. This assumption meant we were always deprecating a loop index ultimately leading to an infinite loop (when using touch input).
Resolution Note (fix version 1.12.0):
Fixed an editor/player hang in `InputSystemUIInputModule` due to an infinite loop. This was caused by the assumption that `RemovePointerAtIndex` would _always_ successfully remove the pointer, which is not the case with touch based pointers.