Search Issue Tracker
Third Party Issue
Votes
0
Found in
2022.3.17f1
2023.2.4f1
2023.3.0b1
6000.0.0b11
Issue ID
UUM-60014
Regression
Yes
[Quest 2] The Player sometimes crashes when the Mixed Reality template is built with Development Build and Vulkan selected
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Switch Platform to Android (File > Build Settings > Android > Switch Platform)
4. Make sure that only the Vulkan Graphics API is selected (Edit > Project Settings > Player > Other Settings > Graphics APIs)
5. Build and Run on Quest 2
6. Observe the Player
7. Repeat steps 5 and 6 for 5 times and give APK a unique name for each build
Expected result: The Player does not crash and continues to run
Actual result: Player crashes
Reproducible with: 2022.3.17f1, 2023.2.4f1, 2023.3.0b1
Not reproducible with: 2021.3.33f1
Reproducible with devices:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Testing environment: Windows 10 Enterprise 21H2, macOS 14.2 23C64 Darwin 23.2.0 (M1) (User’s device)
Not reproducible on: No other environment tested
Notes:
- Not reproducible with Release build
- Does not reproduce with OpenGLES3
- Reproduction is more consistent with 2023.2.4f1 and 2023.3.0b1 versions
- Reproducible with Debugger Enabled and Disabled, but might be more consistent with Enabled
- Does not reproduce with Windows Standalone Player
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
- Animation Clip with Legacy enabled does not play when Time.timeScale is set to 0 despite Update mode set to "Unscaled time"
- Rename is enabled on subfolder empty space - "Can't rename to empty name" warning
- SamplerState Property Missing Anisotropic Filtering
- Visual glitches when using Handles API
- The RGBA color values are inconsistent when comparing two identical colors set in the Inspector
Resolution Note:
The underlying issue is caused by Meta's handling of xrCreateVulkanInstance where they accidentally request duplicate extensions. Confirmed that crash doesn't exist on the v64 software update but did on v63.