Search Issue Tracker
Third Party Issue
Votes
11
Found in [Package]
4.2.0
Issue ID
OXPB-144
Regression
No
[OculusXR] Quest application crashes on launch when using MultiView and OpenGLES3
Steps to reproduce:
1. Open the attached project "Crash Quest - Copy"
2. Switch to Android
3. Open "Assets/Scenes/SampleScene.unity" and include it in the build
4. Build for Quest 2/3
5. Oberve application crashes on startup (if doesn't crash the first time, relaunch and repeat the step until it does)
Expected results: the application does not crash on launch with OculusXR, MultiView and OpenGLES3
Actual result: OculusXR application crashes on launch when using MultiView and OpenGLES3
Reproducible with: OculusXR 4.2.0 (2022.3.20f1, 2023.2.12f1, 2023.3.0b8)
Not reproducible in: OculusXR 4.2.0 (2021.3.35f1)
Testing Environment: Windows 11
Not reproducible on: No other environment tested
Reproducible with devices:
VLNQA00415 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 10
VLNQA00609 - Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, OS: 12
Not reproducible on these devices:
VLNQA00381, Xiaomi Redmi Note 8 Pro (Redmi Note 8 Pro), Android 9, CPU: MediaTek Helios G90T MT6785T, GPU: Mali-G76 MC4
VLNQA00423, Google Pixel 3 (Pixel 3), Android 9, CPU: Snapdragon 845, GPU: Adreno (TM) 630
VLNQA00422, Samsung Galaxy S21 Ultra 5G (SM-G998B), Android 11, CPU: Exynos 2100, GPU: Mali-G78
VLNQA00282, Samsung Galaxy S10e (SM-G970U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00528, Hmd Global Nokia G20 (Nokia G20), Android 13, CPU: Mediatek MT6765G Helio G35 (12 nm), GPU: PowerVR Rogue GE8320
Notes:
-Reproducible only with OculusXR Plugin
-Reproducible only with OpenGLES3 and Release build
-User project contains MetaXR SDK v60.0 packages
-Could not test on OpenXR due to this error when trying to fix Project Validation errors:
NullReferenceException: Object reference not set to an instance of an object
OVRConfigurationTask+<>c_{_}DisplayClass51_0.<ToValidationRule>b{_}_2 () (at ./Library/PackageCache/com.meta.xr.sdk.core@60.0.0/Editor/OVRProjectSetup/Tasks/OVRConfigurationTask.cs:258)
Unity.XR.CoreUtils.Editor.BuildValidator.FixIssues (System.Collections.Generic.IList`1[T] issues, System.String progressBarTitle) (at ./Library/PackageCache/com.unity.xr.core-utils@2.3.0/Editor/ProjectValidation/BuildValidator.cs:156)
-Stack trace first 5 lines:
#00 pc 0000000000083894 /apex/com.android.runtime/lib64/bionic/libc.so (memset+84) (BuildId: e3d79374e2f39224498e405166a48a38)
#01 pc 0000000000c521fc /data/app/~~UJ5f_S6Dvsxpt9Eim0_82w==/com.DefaultCompany.CrashQuest-6HYYbh_gpEDhqOvyVhpiyw==/lib/arm64/libunity.so (ApiGLES::ClearBufferSubData(unsigned int, gl::BufferTarget, long, long)+164) (BuildId: 69a1005243b2a59f)
#02 pc 0000000000c2d968 /data/app/~~UJ5f_S6Dvsxpt9Eim0_82w==/com.DefaultCompany.CrashQuest-6HYYbh_gpEDhqOvyVhpiyw==/lib/arm64/libunity.so (BufferManagerGLES::AcquireBuffer(unsigned long, DataBufferGLES::BufferUsage, GfxBuffer*, bool)+572) (BuildId: 69a1005243b2a59f)
#03 pc 0000000000c41e28 /data/app/~~UJ5f_S6Dvsxpt9Eim0_82w==/com.DefaultCompany.CrashQuest-6HYYbh_gpEDhqOvyVhpiyw==/lib/arm64/libunity.so (GfxDeviceGLES::UpdateComputeConstantBuffers(unsigned int, ConstantBufferHandle*, unsigned)
#04 pc 0000000000e1411c /data/app/~~UJ5f_S6Dvsxpt9Eim0_82w==/com.DefaultCompany.CrashQuest-6HYYbh_gpEDhqOvyVhpiyw==/lib/arm64/libunity.so (GfxDeviceWorker::RunCommand(ThreadedStreamBuffer&)+18760) (BuildId: 69a1005243b2a59f)
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
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
Resolution Note:
This has been identified at a Meta issue. We've passed along the issue to them.