Search Issue Tracker
Fixed
Fixed in 2021.3.16f1
Votes
2
Found in
2021.3.14f1
2022.1.23f1
Issue ID
UUM-19899
Regression
Yes
Crash on MainMessageLoop when changing Input Systems
How to reproduce:
# Open the user attached “Survivors.zip” project
# Go to Edit > Project Settings…
# In the Project Settings go to Player > Configuration > Active Input Handling*
# Switch between Input System Package (New) and Input Manager (Old)
# Observe the crash
Reproducible with: 2022.1.18f1, 2022.1.23f1
Not reproducible with: 2020.3.42f1, 2021.3.14f1, 2022.1.0a1, 2022.1.17f1, 2022.2.0a1, 2022.2.0b16, 2023.1.0a20
Reproduced on: Windows 10 (Intel)
First lines of stack trace:
0x00007ff69c7c1218 (Unity) MainMessageLoop
0x00007ff69c7c6024 (Unity) WinMain
0x00007ff69db3b96e (Unity) __scrt_common_main_seh
0x00007ff8970c74b4 (KERNEL32) BaseThreadInitThunk
0x00007ff898da26a1 (ntdll) RtlUserThreadStart
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Main Camera rendering is being overwritten by a UI Camera when using multiple cameras with URP and the second camera's background type is set to "Uninitialized"
- VisualTreeAsset has significantly increased memory allocation size at runtime when the project is built with IL2CPP scripting backend
- NullReferenceException is logged when cancelling Shader Graph recovery of an already deleted Shader Graph
- White Edges appear during Camera movement in runtime when using FSR2 with Motion Vectors and Exposure enabled
- Lens Flare renders without occlusion when the light source is obstructed by solid objects when running on Android using OpenGL
Add comment