Meta's handling of xrCreateVulkanInstance requests duplicate extensions, causing crashes
Trying to execute a VR game with Vulkan when OpenXR runtime is set to Meta causes crashes before the application starts, although not always. I have checked with an empty Unity project that it only happens with Vulkan and Meta runtime environment. After much searching, it led me to this thread on the Unity forums from late 2023, early 2024, where someone from the support team clarifies that it is a problem on Meta's part, and they make that clear in this bug report. It's been over a year since this bug was reported to Meta by Unity itself and it still hasn't been fixed, we're unable to progress in the development of our game because of this bug. We need a fix for this critical bug ASAP.128Views3likes0Comments
Oculus Link crashes when Unity enters PlayMode and does not work until Unity Editor is restarted
As described in the discussion title. More often than not does Oculus Link crash out of existence when entering Unity´s play mode. The setup is as follows. I use an official Oculus USB-C cable to connect my Oculus Quest to my Windows10 PC while using any Unity version past 2019 (prev. versions not tested) with the Unity build in XR Oculus package (not the Oculus Integration from the AssetStore). The idea now is that when I press Play in the Unity editor I will be able to test my app in a similar way as if it was installed on the Quest directly. This worked without any issues until some recent Oculus update (can´t tell when exactly) which apparently let´s the Oculus Link app crash very often regardless of Unity Version or complexity of the scene. The Quest itself gets thrown back into the standard Quest homescreen, Unity will just be stuck on a black screen and the Oculus app will restart anew after its disappearance. That by itself is annoying enough. But the main problem is that I cannot just exit Unity play mode, reestablish the Oculus Link and enter play mode again to fix the problem. Oh no! The major time consuming part of this misbehavior is that once it crashed I need to close the Unity editor, then restart Oculus Link, then start the Unity editor again. Imagine having a semi-big project with an active collaborate service checking for changes every time Oculus Link decides to crash and forcing you to restart the editor. Please help. I do not know how to solve this. If someone at least knows a workaround or fix that does spare me from restarting the editor, I´d be more than happy.4.8KViews3likes4CommentsUnity game loading then crashing on Meta Quest 2
Hello! I am making a VR game in Unity, and when I try to launch it, it gives a splash screen, then crashes. It works fine in the Unity Editor, but when I sideload it to the quest, it does it. And note that It was working fine before (When we built other versions earlier back) then, I had not added any packages or anything. When I was on one of the previous builds, (Which was unaffected before) It just started doing it for no reason. I released a new version in an attempt to fix it, but it didn't work. This is a video of what I mean by "crashing", and This is the Oculus Logs File I received from MQDH. Thank you. If you need any more info, let me know.912Views0likes0Comments
Unity editor crash with openXR on startup
I'm using Oculus SDK inside Unity and whenever I try to run Unity with no headset attached it crashes. I've opened a bug report with full logs given to them and they've concluded that the problem was the oculus sdk. They send me this saying this is the cause of problem : 0x00007fff76fd6ad7 (LibOVRRT64_1) ovr_ReleaseHapticsClip 0x00007fff76f9e902 (LibOVRRT64_1) ovr_ReleaseHapticsClip 0x00007fff66610876 (OVRPlugin) ovrp_UnityOpenXR_OnSessionDestroy2.1KViews2likes2Comments
Quest 2 Unity built app Crash with signal 11 (SIGSEGV), code 2 (SEGV_ACCERR)
Hi, I am having a crashing bug on the Quest 2 with Unity version 2022.1.23f1 and the 49 release of the Integration SDK. Here's the crash portion of the log. 21:07:28.264 6514 6578 E CRASH : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 21:07:28.264 6514 6578 E CRASH : Version '2022.1.23f1 (9636b062134a)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a' 21:07:28.264 6514 6578 E CRASH : Build fingerprint: 'oculus/hollywood/hollywood:10/QQ3A.200805.001/49882890235800150:user/release-keys' 21:07:28.264 6514 6578 E CRASH : Revision: '0' 21:07:28.264 6514 6578 E CRASH : ABI: 'arm64' 21:07:28.264 6514 6578 E CRASH : Timestamp: 2023-02-23 21:07:28-0600 21:07:28.264 6514 6578 E CRASH : pid: 6514, tid: 6578, name: Thread-2 >>> com.robertdiel.hidden <<< 21:07:28.264 6514 6578 E CRASH : uid: 10130 21:07:28.264 6514 6578 E CRASH : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x79f0402000 21:07:28.264 6514 6578 E CRASH : x0 0000007927afe000 x1 00000079f0401fd0 x2 00000000000000e0 x3 0000007927afe1c0 21:07:28.264 6514 6578 E CRASH : x4 00000079f0402100 x5 0000007927afe330 x6 0000000000000000 x7 0000000000000000 21:07:28.264 6514 6578 E CRASH : x8 0000000000000000 x9 0000000000000000 x10 0000007a202723b0 x11 0000000000000000 21:07:28.264 6514 6578 E CRASH : x12 0000000000000000 x13 0000000000000000 x14 0000000000000000 x15 0000000000000000 21:07:28.264 6514 6578 E CRASH : x16 0000007a4901c980 x17 0000007b3007dec0 x18 0000007966fc4000 x19 00000000000000a0 21:07:28.264 6514 6578 E CRASH : x20 00000079c0bc9b40 x21 00000079f0401dd0 x22 0000007927afe000 x23 0000000000000330 21:07:28.264 6514 6578 E CRASH : x24 0000007a2031ad40 x25 0000000000000330 x26 00000079c03c9740 x27 0000007967f4dab0 21:07:28.264 6514 6578 E CRASH : x28 0000000000002792 x29 0000007967f4dc20 21:07:28.264 6514 6578 E CRASH : sp 0000007967f4d840 lr 0000007a4854c418 pc 0000007b3007de74 21:07:28.264 6514 6578 E CRASH : 21:07:28.264 6514 6578 E CRASH : backtrace: 21:07:28.264 6514 6578 E CRASH : #00 pc 000000000007ce74 /apex/com.android.runtime/lib64/bionic/libc.so (je_malloc_tsd_boot0+476) (BuildId: 76160b7be02961a2e357c92bde57eb19) 21:07:28.264 6514 6578 E CRASH : #01 pc 0000000000869a64 /data/app/com.robertdiel.hidden-me9IVjKY7GEU8XDjXFoKTA==/lib/arm64/libunity.so (BuildId: c913ccde1ef67c65a670e3b7ea4cba438b4408a4) This crash only happens once at the beginning of the run, but when I exit and restart the app from the device, the crash doesn't occur again. I did some investigation and found out that this is an Execution-Only memory violation, and that someone with a similar problem updated the SDK and it solved the issue. This wasn't the case for me. Has anyone had this issue and found a solution?2.8KViews1like1Comment
Unity Editor Crash Using OVRLipSync On MacOS
I'm hitting a strange issue that I can't explain. We're developing a VR app in Unity and I've recently added the OVRLipSync for mouth movements but I keep getting Unity Editor crashes every time I run our application, even in the sample scene included in the package - It's 100% reproduceable. I have noticed however if we create a whole new Unity project (same Unity Editor version) and import the OVRLipSync package then run the sample scene it works fine (obvious after allowing permissions to the bundle file via System Preferences). However the crashes are consistent in our own project we're trying to add OVRLipSync to, so something is definitely amiss in my project specifically. It's also worth noting that it is only crashing on OSX, not Windows - I only have one OSX device so it could be specific to my Macbook but I'm unable to confirm that. At first I thought maybe it was OSX not having permission to the OVRLipSync.bundle file but I've ruled this out as I've re-imported the bundle file and allowed permission via the System Preferences -> Allow Anyway option. If anyone is able to help it'd be a huge relief as this is causing us a lot of issues at the moment as we're having to add defines in our code to ensure nothing involving the lipsync is used when we're developing in OSX. Here's my Editor.log file: OvrLipSync Awake: Queried SampleRate: 44100 BufferSize: 512 UnityEngine.StackTraceUtility:ExtractStackTrace () (at /Users/bokken/buildslave/unity/build/Runtime/Export/Scripting/StackTrace.cs:37) UnityEngine.DebugLogHandler:LogFormat (UnityEngine.LogType,UnityEngine.Object,string,object[]) UnityEngine.Logger:Log (UnityEngine.LogType,object) UnityEngine.Debug:LogWarning (object) OVRLipSync:Initialize () (at Assets/Oculus/LipSync/Scripts/OVRLipSync.cs:265) OVRLipSync:Awake () (at Assets/Oculus/LipSync/Scripts/OVRLipSync.cs:217) (Filename: Assets/Oculus/LipSync/Scripts/OVRLipSync.cs Line: 265) Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle.dylib Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle.so Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle E1115 10:21:07.861620 399812096 init_intrinsics_check.cc:44] CPU feature avx2 is present on your machine, but the Caffe2 binary is not compiled with it. It means you may not get the full speed of your CPU. E1115 10:21:07.862260 399812096 init_intrinsics_check.cc:44] CPU feature fma is present on your machine, but the Caffe2 binary is not compiled with it. It means you may not get the full speed of your CPU. Loaded scene 'Temp/__Backupscenes/0.backup' Deserialize: 64.066 ms Integration: 493.917 ms Integration of assets: 0.970 ms Thread Wait Time: -0.236 ms Total Operation Time: 558.717 ms Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle.dylib Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle.so Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle.dylib Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle.so Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle *** Aborted at 1668507668 (unix time) try "date -d @1668507668" if you are using GNU date *** PC: @ 0x193b3b4f3 (unknown) *** SIGSEGV (@0x0) received by PID 2995 (TID 0x117d4a600) stack trace: *** @ 0x7ff8074c2dfd _sigtramp1.3KViews0likes0CommentsQuest 2 crash on trigger input
Unity: 2020.3.18f1 Hello, I am developing an application in Unity and running it on the Quest 2. It is initialized after Runtime with XRGeneralSettings.Instance.Manager.InitializeLoaderSync(); XRGeneralSettings.Instance.Manager.StartSubsystems(); And I am am able to enter the space and move around and jump, but when I provide input through the triggers, the headset seems to crash; it fades to black and the hourglass appears forever. I have not assigned anything fancy to those inputs; I don't know why they would crash. I have android Dev set up and am using Oculus XR Plugin OpenXR Plugin XR Interaction Toolkit XR Plugin Management. I am also not able to exit VR smoothly; the headset crashes but the app continues to run in unity engine. Can anyone provide any guidance? I am new to VR dev.1KViews0likes0Comments
LoadScene crashes on Oculus Quest
Oculus Quest Unity 2019.3.0f6 Oculus Android 2.38.6 Calling SceneManager.LoadScene(levelName) to change scene will crash on device while it is working fine in the editor. I have tried with a full path and with the index, it always crashes. I have opened the APK, under assets/bin/Data, I see sharedassets0.resource and sharedassets1.resource which I am guessing are my 2 scenes that are stored in the APK. Am I missing something obvious, some extra step that I am unaware of when trying to load a scene from a Quest? Here is the Console Log: --------- beginning of crash 01-30 00:47:19.855 712 22100 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 22100 (Mapper0) 01-30 00:47:21.104 22116 22116 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 01-30 00:47:21.104 22116 22116 F DEBUG : Build fingerprint: 'oculus/vr_monterey/monterey:7.1.1/NGI77B/434260.5710.0:user/release-keys' 01-30 00:47:21.104 22116 22116 F DEBUG : Revision: '0' 01-30 00:47:21.104 22116 22116 F DEBUG : ABI: 'arm64' 01-30 00:47:21.105 22116 22116 F DEBUG : pid: 712, tid: 22100, name: Mapper0 >>> /system/bin/trackingservice <<< 01-30 00:47:21.105 22116 22116 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr -------- 01-30 00:47:21.109 22116 22116 F DEBUG : Abort message: 'Check '0 <= pIndex < map_.num_points()' failed 01-30 00:47:21.109 22116 22116 F DEBUG : 0: 0 01-30 00:47:21.109 22116 22116 F DEBUG : pIndex: -1 01-30 00:47:21.109 22116 22116 F DEBUG : map_.num_points(): 515 01-30 00:47:21.109 22116 22116 F DEBUG : ' 01-30 00:47:21.109 22116 22116 F DEBUG : x0 0000000000000000 x1 0000000000005654 x2 0000000000000006 x3 0000000000000008 01-30 00:47:21.109 22116 22116 F DEBUG : x4 0000007f72994630 x5 000000000000003f x6 0000000000000001 x7 00000055593fded4 01-30 00:47:21.109 22116 22116 F DEBUG : x8 0000000000000083 x9 0000007f72995450 x10 b155ed72af558bdb x11 0000000000000000 01-30 00:47:21.109 22116 22116 F DEBUG : x12 0000000000000001 x13 0000000000000020 x14 ffffffffffffffdf x15 0032fb449cad3104 01-30 00:47:21.109 22116 22116 F DEBUG : x16 0000007f9888cec8 x17 0000007f9882ded0 x18 000000000000005f x19 0000007f729954f8 01-30 00:47:21.109 22116 22116 F DEBUG : x20 0000000000000006 x21 0000007f72995450 x22 0000000000000000 x23 0000007f65bef200 01-30 00:47:21.109 22116 22116 F DEBUG : x24 0000007f6d9ca588 x25 0000007f7c828e20 x26 0000000000000043 x27 0000007f65bef250 01-30 00:47:21.109 22116 22116 F DEBUG : x28 bfbb0ee54fad38fa x29 0000007f729944f0 x30 0000007f9882ac84 01-30 00:47:21.109 22116 22116 F DEBUG : sp 0000007f729944d0 pc 0000007f9882ded8 pstate 0000000060000000 01-30 00:47:21.127 22116 22116 F DEBUG : 01-30 00:47:21.127 22116 22116 F DEBUG : backtrace: 01-30 00:47:21.127 22116 22116 F DEBUG : #00 pc 0000000000079ed8 /system/lib64/libc.so (tgkill+8) 01-30 00:47:21.127 22116 22116 F DEBUG : #01 pc 0000000000076c80 /system/lib64/libc.so (pthread_kill+64) 01-30 00:47:21.127 22116 22116 F DEBUG : #02 pc 0000000000024ac0 /system/lib64/libc.so (raise+24) 01-30 00:47:21.127 22116 22116 F DEBUG : #03 pc 000000000001cdcc /system/lib64/libc.so (abort+52) 01-30 00:47:21.127 22116 22116 F DEBUG : #04 pc 0000000000003d58 /system/bin/trackingservice (__android_log_assert+224) 01-30 00:47:21.127 22116 22116 F DEBUG : #05 pc 0000000000b919a0 /system/lib64/libMontereyTracker.so (_ZN9visionlog12doLogFatalOpIRKiRiRmJEEEvOT_PKcOT0_S8_OT1_S8_S8_S8_DpOT2_+192) 01-30 00:47:21.127 22116 22116 F DEBUG : #06 pc 0000000001070760 /system/lib64/libMontereyTracker.so (_ZN5viper29VisualBundleAdjustmentProblem38createAllReprojectionErrorsForKeyframeERNS_8KeyframeEb+732) 01-30 00:47:21.127 22116 22116 F DEBUG : #07 pc 00000000010702ac /system/lib64/libMontereyTracker.so (_ZN5viper29VisualBundleAdjustmentProblem15initializeLocalERNSt6__ndk16vectorIiN9optimizer9allocator13PoolAllocatorIiEEEERNS1_3setIiNS1_4lessIiEES6_EE+3020) 01-30 00:47:21.127 22116 22116 F DEBUG : #08 pc 000000000112704c /system/lib64/libMontereyTracker.so (_ZN5viper21localBundleAdjustmentEiiiRNS_23BundleAdjustmentProblemEPNSt6__ndk16vectorIiNS2_9allocatorIiEEEES7_+1460) 01-30 00:47:21.127 22116 22116 F DEBUG : #09 pc 0000000000ed6c14 /system/lib64/libMontereyTracker.so (_ZN5viper17ViperMapOptimizer24wrappedLocalBundleAdjustERNS_3MapEiiPNSt6__ndk16vectorIiNS3_9allocatorIiEEEE+244) 01-30 00:47:21.127 22116 22116 F DEBUG : #10 pc 0000000000ed7784 /system/lib64/libMontereyTracker.so 01-30 00:47:21.127 22116 22116 F DEBUG : #11 pc 0000000001209ebc /system/lib64/libMontereyTracker.so (_ZN5viper27MapBundleAdjustmentStrategy25runBundleAdjustFuncIfTimeEN13enum_wrapper_22BundleStrategySizeImplERKNSt6__ndk18functionIFNS1_24BundleAdjusterStatusImplEvEEE+60) 01-30 00:47:21.127 22116 22116 F DEBUG : #12 pc 0000000000ed6204 /system/lib64/libMontereyTracker.so (_ZN5viper17ViperMapOptimizer3runERNS_3MapE+316) 01-30 00:47:21.127 22116 22116 F DEBUG : #13 pc 0000000000ec56e0 /system/lib64/libMontereyTracker.so (_ZN5viper11ViperMapper13process_queueEv+456) 01-30 00:47:21.127 22116 22116 F DEBUG : #14 pc 0000000000ec3ec4 /system/lib64/libMontereyTracker.so (_ZN5viper11ViperMapper18process_queue_loopEv+204) 01-30 00:47:21.127 22116 22116 F DEBUG : #15 pc 0000000000ec88c0 /system/lib64/libMontereyTracker.so (_ZNSt6__ndk114__thread_proxyINS_5tupleIJNS_10unique_ptrINS_15__thread_structENS_14default_deleteIS3_EEEEMN5viper11ViperMapperEFvvEPS8_EEEEEPvSD_+64) 01-30 00:47:21.127 22116 22116 F DEBUG : #16 pc 0000000000076454 /system/lib64/libc.so (_ZL15__pthread_startPv+204) 01-30 00:47:21.127 22116 22116 F DEBUG : #17 pc 000000000001e204 /system/lib64/libc.so (__start_thread+16) 01-30 00:47:21.655 1061 1220 W NativeCrashListener: Couldn't find ProcessRecord for pid 712 01-30 00:47:21.665 1061 1118 I BootReceiver: Copying /data/tombstones/tombstone_02 to DropBox (SYSTEM_TOMBSTONE) 01-30 00:47:22.508 1061 1250 I ActivityManager: START u0 {act=com.oculus.vrshell.intent.action.LAUNCH flg=0x10000000 cmp=com.oculus.vrshell/.MainActivity (has extras)} from uid 10024 on display 0 01-30 00:47:27.295 1061 1563 I ActivityManager: START u0 {act=com.oculus.vrshell.intent.action.LAUNCH flg=0x10000000 cmp=com.oculus.vrshell/.MainActivity (has extras)} from uid 10024 on display 0 01-30 00:47:29.841 1061 1207 E TaskPersister: File error accessing recents directory (directory doesn't exist?).2.5KViews0likes4Comments
App using AppLab package name cannot start
We started the submission process for AppLab with a very specific package name. When we try to build and run the app that uses that package name, the app doesn't start and when it's launched it just stops and you get back to the main oculus menu. Whatever other package name works fine, that is the only difference between working builds and not working ones. Has this issue ever occurred to anyone else? This specific thing, is really blocking for the review progress, of course.704Views0likes0Comments
Native Crash - Unknown Function (/system/app/Horizon/Horizon.apk)
For some reason, Oculus SDK is trying to access Horizon during the runtime of my application. Would anyone happen to know why or how to disable it or if someone from Oculus would tell us when this is going to be fixed?790Views1like0Comments
Meta's handling of xrCreateVulkanInstance requests duplicate extensions, causing crashes
Trying to execute a VR game with Vulkan when OpenXR runtime is set to Meta causes crashes before the application starts, although not always. I have checked with an empty Unity project that it only happens with Vulkan and Meta runtime environment. After much searching, it led me to this thread on the Unity forums from late 2023, early 2024, where someone from the support team clarifies that it is a problem on Meta's part, and they make that clear in this bug report. It's been over a year since this bug was reported to Meta by Unity itself and it still hasn't been fixed, we're unable to progress in the development of our game because of this bug. We need a fix for this critical bug ASAP.
