Search Issue Tracker
Fixed
Fixed in 2021.3.10f1, 2022.1.15f1, 2022.2.0a6
Votes
2
Found in
2021.3.5f1
2022.1.6f1
2022.2.0a5
Issue ID
UUM-6726
Regression
No
[XR][Vulkan] Crash on "vkResetFences" when entering Play mode
Reproduction steps:
# Open the user's attached project
# Open Assets > Scenes > “ControllerSample”
# Enter Play mode
Expected result: Play mode gets loaded
Actual result: Crash
Reproduced with: 2021.3.5f1, 2022.1.6f1, 2022.2.0a5
Not reproduced with: 2022.2.0a6, 2022.2.0a17
Could not test with: 2019.4.40f1 (too many errors), 2020.3.36f1 (error “Attempting to determine the size of an unknown feature type Id \[-1].”)
Reproducible on: Windows 11
Stacktrace:
0x00007FF9E9A9578A (vulkan-1) vkResetFences
0x00007FF6C02A2AF5 (Unity) GfxDeviceVK::InsertCustomMarkerCallbackAndData
0x00007FF6C17B1084 (Unity) GfxDeviceWorker::RunCommand
0x00007FF6C17B77DD (Unity) GfxDeviceWorker::RunExt
0x00007FF6C17B78F8 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FF6BFEADD07 (Unity) Thread::RunThreadWrapper
0x00007FFA5A417034 (KERNEL32) BaseThreadInitThunk
0x00007FFA5AB82651 (ntdll) RtlUserThreadStart
Notes:
* Sometimes crash does not occur instantly when entering Play mode, so you need to exit and enter Play mode again
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 2022.2.0a6):
Fixed in: 2022.2.0a6
Resolution Note (fix version 2022.1.15f1):
Fixed in: 2022.1.15f1
Resolution Note (fix version 2021.3.10f1):
Fixed in: 2021.3.10f1