Search Issue Tracker
Fixed in 1.1-pre.5
Votes
0
Found in [Package]
1.1.0-preview.3
Issue ID
1316000
Regression
No
Crash when adding InputSystem.Update() to InputSystem command handler to force processing an event and sending input
How to reproduce:
1. Open the attached project ('InputSystemUnityCrashBug.zip')
2. Enter Play Mode
3. Click the up and down arrow keys (using the keyboard) a few times
Reproducible with: 2020.2.6f1, 2021.1.0b7, 2021.2.0a5 (1.1.0-preview.1, 1.1.0-preview.3)
Could not test with: 2018.4.32f1, 2019.4.20f1 (errors when downgrading)
Could not test with package version: 1.0.2 ('IInputActionCollection2' not yet implemented)
Notes:
This error message might appear before the crash: 'StackOverflowException: The requested operation caused a stack overflow.'
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 1.1-pre.5):
the bug is fixed now in the sense that users are not allowed to call InputSystem.Update() from inside an input system action handler.