Search Issue Tracker
Fixed in 1.1-preview
Votes
0
Found in [Package]
1.0.0
Issue ID
1262496
Regression
No
[Input System] Crash with various stack traces when using InputActionTrace.SubscribeToAll
How to reproduce:
1. Download tester-attached package (CrashPackage.unitypackage)
2. Create a new Unity project, import the Input System package and create its settings asset
3. Import the CrashPackage
4. Open the CrashScene and enter Play Mode
5. Click around the Scene/Game view, if the crash does not occur, try exiting/entering Play Mode again
Expected result: the Editor does not crash
Actual result: the Editor crashes
Reproducible with: 2019.4.4f1, 2020.1.0b16, 2020.2.0a18(Input System preview - 0.9.1, 1.0.0)
Could not test with: 2018.4.25f1(affected package version unavailable), 2019.4.4f1, 2020.1.0b16, 2020.2.0a18(Input System preview - 0.9.0 - InputActionTrace not implemented)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 1.1-preview):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1184