Forum Discussion
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:
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?).
4 Replies
Replies have been turned off for this discussion
- Any luck? Facing the same problem here...
- Update - the crash I am experiencing is very similar to this post:
https : //forum.unity.com/ threads/ crash-during-scene-change-unload.568138/
(remove the space, forum wouldn't let me post a link otherwise)I found it it only crashes when unloading a large scene. I am probably doing something that exposes this bug. My workaround will be to never unload a scene, instead additive load on an empty scene and delete every object and additive load another scene when changing map.
I hope this will work.At the end that workaroud fixed the problem?
- Update - An empty scene on a fresh project on the same Unity version, same Oculus version is working without problems.An empty scene in my existing project loading the same empty scene crashes...There is has to be a setting somewhere in my project that makes it crash...I have tried to change the compression method, but that makes no difference...
