Search Issue Tracker
In Progress
Fix In Review for 2022.3.56f1, 6000.0.X
Fixed in 6000.1.0a8
Votes
5
Found in
2020.3.39f1
2021.3.7f1
2022.2.0b8
2023.1.0a12
2023.2.0a1
6000.0.0b11
7000.0.0a1
Issue ID
UUM-10774
Regression
No
Crash on InputDeviceIOCTL when closing Unity editor
Reproduction steps:
1. Open the user’s attached project
2. Enter Play mode
3. Close Unity Editor
Expected result: Editor closes successfully
Actual result: Editor crashes
Reproducible with: 2021.2.0a18, 2021.2.19f1, 2021.3.7f1
Not reproducible with: 2020.3.37f1, 2021.1.28f1, 2021.2.0a17, 2022.1.0a1, 2022.1.12f1, 2022.2.0b3, 2023.1.0a5
Reproducible on: Windows 10 Pro 21H2
Notes:
* You have to reimport the project on every version
* Crash sometimes does not reproduce
* Sometimes crash reproduces when just opening and closing the Unity Editor
* Crash can sometimes only reproduce when waiting in Play mode for a few minutes and then closing Unity Editor
First lines of the stack trace:
{noformat}0x00007FF7BDAD97CE (Unity) InputDeviceIOCTL
0x00007FF7BCA6259E (Unity) NativeInputSystem_CUSTOM_IOCTL
0x0000023E643D546A (Mono JIT Code) (wrapper managed-to-native) UnityEngineInternal.Input.NativeInputSystem:IOCTL (int,int,intptr,int)
0x0000023E643D4FF3 (Mono JIT Code) [C:\Cases\IN-10955\Library\PackageCache\com.unity.inputsystem@1.4.1\InputSystem\NativeInputRuntime.cs:46] UnityEngine.InputSystem.LowLevel.NativeInputRuntime:DeviceCommand (int,UnityEngine.InputSystem.LowLevel.InputDeviceCommand*)
0x0000023E643D4D59 (Mono JIT Code) [C:\Cases\IN-10955\Library\PackageCache\com.unity.inputsystem@1.4.1\InputSystem\Devices\InputDevice.cs:581] UnityEngine.InputSystem.InputDevice:ExecuteCommand (UnityEngine.InputSystem.LowLevel.InputDeviceCommand*) {noformat}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment