Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.4
2019.3
2020.1
2020.1.0b8
Issue ID
1250096
Regression
No
Crash on win::XInputDevice::Poll when closing the editor
The crash occurs when closing the Unity engine but cannot be reproduced reliably.
Reproducible on (according to user reports): 2018.4.20f1, 2019.3.14f1, 2020.1.0b8.
Full stack trace:
0x00007FF77097AFDA (Unity) win::XInputDevice::Poll
0x00007FF76F5AC0AA (Unity) InputPollingLoop
0x00007FF770652C40 (Unity) Thread::RunThreadWrapper
0x00007FFD621A7BD4 (KERNEL32) BaseThreadInitThunk
0x00007FFD623ACE51 (ntdll) RtlUserThreadStart
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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a15