Search Issue Tracker
Third Party Issue
Votes
0
Found in [Package]
1.9.1
Issue ID
OXRB-291
Regression
No
[Quest][OpenXR] Development Quest build crashes on start when using MetaXR SDK and OpenXR with Vulkan
Steps to reproduce:
1. Open the attached user's project "TestApp.zip"
2. Make sure MetaXR SDK is installed via Unity Asset Store
3. Make sure Development build and OpenXR are enabled
4. Build for Quest 2/3
Expected Result: Application does not crash
Actual Result: Application crashes
Reproducible with: OpenXR 1.8.2, 1.9.1 (2022.3.18f1, 2023.2.7f1, 2023.3.0b4)
Not reproducible on: OpenXR 1.9.2 (2021.3.34f1)
Could not test below 2022.3.5f1 due to MetaXR SDK outputting errors when downgrading
Reproducible with these devices:
VLNQA00609 - Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, OS: 12
VLNQA00415 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 12
Testing Environment: Windows 11
Not reproducible on: No other environment tested
Notes:
-Crash does not reproduce when using OculusXR
-Crash reproduces only when Development build is enabled
-4 Lines of stacktrace:
#00 pc 00000000002636bc /vendor/lib64/hw/vulkan.adreno.so (qglinternal::vkCreateInstance(VkInstanceCreateInfo const*, VkAllocationCallbacks const*, VkInstance_T**)+1020) (BuildId: 2b509cc06a65958aa24fe7fcbd32c0d4)
2024/01/21 19:52:29.998 18440 18465 Error CRASH #01 pc 000000000001cb6c /system/lib64/libvulkan.so (BuildId: a4fdc99223ddc46513377df1e2d8b6cf)
2024/01/21 19:52:29.998 18440 18465 Error CRASH #02 pc 0000000000012518 /system/lib64/libvulkan.so (BuildId: a4fdc99223ddc46513377df1e2d8b6cf)
2024/01/21 19:52:29.998 18440 18465 Error CRASH #03 pc 00000000002e9444 /system/priv-app/VrDriver/VrDriver.apk (BuildId: cf2d223e82c25060700bd14594f4a18444643058)
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
- ScrollView speed is slower when entering Play mode
- UI Builder elements disappear and "Semantic - Unknown template name" error appears when changes to "Template" parameter are saved
- Renderers outside Light Probe hull use incorrect Ambient Probe values when "Renderer Light Probe Selection" is set to "Use Ambient Probe" and "Light Probes" on Mesh is set to "Blend Probes"
- ArgumentNullException error occurs when selecting a Camera in the Hierarchy with the Scene view open
- Clicking 'Open Editor Log' through the Console fails to open redirected Logs when relative Log files exist outside of the Project root
Resolution Note:
We've heard back and the underlying issue is caused by Meta's handling of xrCreateVulkanInstance where they accidentally request duplicate extensions. There's no known workaround until their fix lands, which will be in their v64 software update at the end of March.