Forum Discussion
System crash help, and how to get system logs from users?
TLDR; I'd like for a way for my game code (unity) to be able to pull logs out of logcat, not tagged by my game (with the user's permission).....and...maybe someone from Oculus can help resolve why these crashes are happening at all.
During the playing of my game, there are sometimes hard crashes to the system, or even full freezes where users have to hard restart the headset.
I don't know what is causing it. It isn't repeatable consistently....and while it happens more during my game, the stack trace doesn't mention my game at all when it does crash.
I'd like to be able to, on the next game session, offer the user a button that says "would you like to send crash logs from the previous session to help us resolve it?"
I already have a system that allows them to send logs from my own logging...but the few crashes that I have seen, the logs weren't fired from the application.
..but I don't know how to, and if it's possible to pull system ADB logs, from c# unity game context.
When I force a crash from the game through various means (on purpose) the stack mentions the game
below is one from when it crashed during the QA testing
but when it crashes spontaneously during game play it looks like the large paste above...or like this one (specifically captured during a crash)
During the playing of my game, there are sometimes hard crashes to the system, or even full freezes where users have to hard restart the headset.
I don't know what is causing it. It isn't repeatable consistently....and while it happens more during my game, the stack trace doesn't mention my game at all when it does crash.
I'd like to be able to, on the next game session, offer the user a button that says "would you like to send crash logs from the previous session to help us resolve it?"
I already have a system that allows them to send logs from my own logging...but the few crashes that I have seen, the logs weren't fired from the application.
..but I don't know how to, and if it's possible to pull system ADB logs, from c# unity game context.
When I force a crash from the game through various means (on purpose) the stack mentions the game
Build fingerprint: 'oculus/vr_monterey/monterey:7.1.1/NGI77B/358570.9320.0:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 7827, tid: 7842, name: UnityMain >>> quest.eleven.forfunlabs <<<
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xeaa8afb4
r0 cfdfff73 r1 d1d9adc8 r2 eaa8bc44 r3 00000001
r4 eaa8b558 r5 eaa8b560 r6 eaa8b60c r7 eaa8b588
r8 eaa8bc44 r9 d1d9adc8 sl d1d9adc8 fp 00000007
ip ec4b0dd0 sp eaa8af00 lr ec46d70d pc ec467990 cpsr 200f0030
backtrace:
#00 pc 0003f990 /system/lib/libc.so (__vfprintf+27)
#01 pc 00045709 /system/lib/libc.so (vsnprintf+136)
#02 pc 000040f9 /system/lib/liblog.so (__android_log_vprint+40)
#03 pc 002eedfc /data/app/quest.eleven.forfunlabs-1/lib/arm/libunity.so
#04 pc 00773d50 /data/app/quest.eleven.forfunlabs-1/lib/arm/libunity.so
#05 pc 002ee72c /data/app/quest.eleven.forfunlabs-1/lib/arm/libunity.so
#06 pc 00001d0c [anon:thread signal stack:eaa8b000]
below is one from when it crashed during the QA testing
but when it crashes spontaneously during game play it looks like the large paste above...or like this one (specifically captured during a crash)
--------- beginning of crash
08-21 07:55:40.946 709 5076 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 5076 (CamSlamCfsMgr)
08-21 07:55:41.428 5662 5662 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-21 07:55:41.429 5662 5662 F DEBUG : Build fingerprint: 'oculus/vr_monterey/monterey:7.1.1/NGI77B/333700.3780.0:user/release-keys'
08-21 07:55:41.429 5662 5662 F DEBUG : Revision: '0'
08-21 07:55:41.429 5662 5662 F DEBUG : ABI: 'arm64'
08-21 07:55:41.429 5662 5662 F DEBUG : pid: 709, tid: 5076, name: CamSlamCfsMgr >>> /system/bin/trackingservice <<<
08-21 07:55:41.430 5662 5662 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
08-21 07:55:41.430 5662 5662 F DEBUG : x0 0000000000000000 x1 00000000000013d4 x2 0000000000000006 x3 0000000000000008
08-21 07:55:41.430 5662 5662 F DEBUG : x4 0000007f87802140 x5 0000007f6813c380 x6 0000000000000001 x7 00000001a32607b8
08-21 07:55:41.430 5662 5662 F DEBUG : x8 0000000000000083 x9 0000007f72d02450 x10 3d4648a5ea451e80 x11 0000000000000000
08-21 07:55:41.430 5662 5662 F DEBUG : x12 0000000000000001 x13 0000000000000020 x14 ffffffffffffffdf x15 0000007f87d68810
08-21 07:55:41.430 5662 5662 F DEBUG : x16 0000007f87d5dec0 x17 0000007f87cff824 x18 0000000000000098 x19 0000007f72d024f8
08-21 07:55:41.430 5662 5662 F DEBUG : x20 0000000000000006 x21 0000007f72d02450 x22 0000000000000000 x23 0000000000000004
08-21 07:55:41.430 5662 5662 F DEBUG : x24 0000007f869ee6e0 x25 00000000000003dc x26 000000000000f700 x27 00000000000003e8
08-21 07:55:41.430 5662 5662 F DEBUG : x28 0000007f711ae602 x29 0000007f72cff410 x30 0000007f87cfc5d8
08-21 07:55:41.430 5662 5662 F DEBUG : sp 0000007f72cff3f0 pc 0000007f87cff82c pstate 0000000060000000
08-21 07:55:41.447 5662 5662 F DEBUG :
08-21 07:55:41.447 5662 5662 F DEBUG : backtrace:
08-21 07:55:41.447 5662 5662 F DEBUG : #00 pc 000000000007982c /system/lib64/libc.so (tgkill+8)
08-21 07:55:41.447 5662 5662 F DEBUG : #01 pc 00000000000765d4 /system/lib64/libc.so (pthread_kill+64)
08-21 07:55:41.447 5662 5662 F DEBUG : #02 pc 0000000000024a80 /system/lib64/libc.so (raise+24)
08-21 07:55:41.448 5662 5662 F DEBUG : #03 pc 000000000001cd8c /system/lib64/libc.so (abort+52)
08-21 07:55:41.448 5662 5662 F DEBUG : #04 pc 00000000008f780c /system/lib64/libMontereyTracker.so (_ZN9visionlog12doLogFatalOpIRiS1_JEEEvOT_PKcOT0_S5_S5_DpOT1_+108)
08-21 07:55:41.448 5662 5662 F DEBUG : #05 pc 0000000000d09e18 /system/lib64/libMontereyTracker.so
08-21 07:55:41.448 5662 5662 F DEBUG : #06 pc 000000000117a0b8 /system/lib64/libMontereyTracker.so (_ZN10perception16ImagePyramidBaseIhNS_18ImageHalfSample3x3EE17runInitializationEN3gsl4spanIKPS2_Lln1EEERKNS1_10ParametersENS_31ImagePyramidInitializationStateE+244)
08-21 07:55:41.448 5662 5662 F DEBUG : #07 pc 0000000000ce9238 /system/lib64/libMontereyTracker.so (_ZN10perception8vio_toon16PatchMatcherBolt5matchERKNS0_20PatchMatcherSettingsEN3gsl4spanIKNS0_10MatchQueryELln1EEENS6_IPKNS_11CameraModelELln1EEENS6_IKPNS_16ImagePyramidBaseIhNS_18ImageHalfSample3x3EEELln1EEENS6_IN8coretech12RefuseReasonELln1EEENS6_INS0_16PatchMatchResultELln1EEE+1424)
08-21 07:55:41.448 5662 5662 F DEBUG : #08 pc 0000000000cedb58 /system/lib64/libMontereyTracker.so (_ZN10perception8vio_toon12PatchTracker5trackENS_6IdTmplItNS0_13FrameSetIdTagELb1EEENS0_17VersionedAnchorIdEN3gsl4spanIKN4TooN3SE3IdEELln1EEENS7_IPKNS_11CameraModelELln1EEENS7_IPNS_16ImagePyramidBaseIhNS_18ImageHalfSample3x3EEELln1EEEbRNSt6__ndk16vectorINS0_16TrackMeasurementENSM_9allocatorISO_EEEERNSN_INS0_26TrackToLandmarkAssociationENSP_IST_EEEERNSN_INS0_18RelativeAnchorDataENSP_ISX_EEEERNSN_INS0_7TrackIdENSP_IS11_EEEE+924)
08-21 07:55:41.448 5662 5662 F DEBUG : #09 pc 00000000009d35dc /system/lib64/libMontereyTracker.so (_ZN5viper26MontereyLagunaTrackTracker5trackENS_13LiveTimestampEN10perception6IdTmplItNS2_8vio_toon13FrameSetIdTagELb1EEEN3gsl4spanIKN4TooN3SE3IdEELln1EEENS8_IPKNS2_11CameraModelELln1EEENS8_INSt6__ndk110shared_ptrINS2_16ImagePyramidBaseIhNS2_18ImageHalfSample3x3EEEEELln1EEEbRNSI_6vectorINS4_16TrackMeasurementENSI_9allocatorISQ_EEEERNSP_INS4_26TrackToLandmarkAssociationENSR_ISV_EEEERNSP_INS4_18RelativeAnchorDataENSR_ISZ_EEEERNSP_INS4_7TrackIdE
08-21 07:55:41.448 5662 5662 F DEBUG : #10 pc 00000000009dbbfc /system/lib64/libMontereyTracker.so (_ZN5viper7Tracker5trackERKN4TooN3SE3IdEERKN10perception8OptionalINS1_6VectorILi3EdNS1_8Internal5VBaseEEEEERKNS_11VideoFramesEPKNS_15ImuMeasurementsERKN5boost8optionalINS1_3SO3IdEEEERKNSM_INS8_ILi3EfSA_EEEE+2756)
08-21 07:55:41.448 5662 5662 F DEBUG : #11 pc 0000000000987268 /system/lib64/libMontereyTracker.so (_ZN5viper4Slam4Impl9track_mapERKNS_11VideoFramesEPKNS_15ImuMeasurementsERKN5boost8optionalIN4TooN3SO3IdEEEERKNS9_INSA_6VectorILi3EfNSA_8Internal5VBaseEEEEE+268)
08-21 07:55:41.448 5662 5662 F DEBUG : #12 pc 0000000000976608 /system/lib64/libMontereyTracker.so (_ZN5viper4Slam4Impl14process_framesERKNS_11VideoFramesE+332)
08-21 07:55:41.448 5662 5662 F DEBUG : #13 pc 0000000000992d9c /system/lib64/libMontereyTracker.so (_ZN5viper18VideoFrameAnalyzer4Impl14process_framesERKNS_11VideoFramesE+372)
08-21 07:55:41.448 5662 5662 F DEBUG : #14 pc 000000000098ff4c /system/lib64/libMontereyTracker.so (_ZN5viper18VideoFrameAnalyzer4Impl9on_framesEN10perception6IdTmplItNS2_8vio_toon13FrameSetIdTagELb1EEEN3gsl4spanIKPKhLln1EEENS_13LiveTimestampENS8_IKdLln1EEESF_+1188)
08-21 07:55:41.448 5662 5662 F DEBUG : #15 pc 00000000008e1904 /system/lib64/libMontereyTracker.so (_ZN8coretech23InsideOutTrackingEngine11onImageDataEPK9ImageDatai30ProcessingClockDomainTimestamp+768)
08-21 07:55:41.448 5662 5662 F DEBUG : #16 pc 000000000111b20c /system/lib64/libMontereyTracker.so
08-21 07:55:41.448 5662 5662 F DEBUG : #17 pc 0000000000020a4c /system/vendor/lib64/libdevices.so (_ZN3OVR7Devices21CameraFrameSetManager12sendFrameSetERNSt3__16vectorINS2_10shared_ptrI9ImageDataEENS2_9allocatorIS6_EEEE+560)
08-21 07:55:41.448 5662 5662 F DEBUG : #18 pc 0000000000020c44 /system/vendor/lib64/libdevices.so (_ZN3OVR7Devices21CameraFrameSetManager23processCompleteFrameSetERNS1_8FrameSetERNSt3__16vectorINS4_10shared_ptrI9ImageDataEENS4_9allocatorIS8_EEEERNS4_11unique_lockINS4_5mutexEEE+80)
08-21 07:55:41.448 5662 5662 F DEBUG : #19 pc 000000000001fba4 /system/vendor/lib64/libdevices.so (_ZN3OVR7Devices21CameraFrameSetManager20frameSetOutputWorkerEv+212)
08-21 07:55:41.448 5662 5662 F DEBUG : #20 pc 0000000000020e8c /system/vendor/lib64/libdevices.so (_ZNSt3__114__thread_proxyINS_5tupleIJMN3OVR7Devices21CameraFrameSetManagerEFvvEPS4_EEEEEPvS9_+116)
08-21 07:55:41.448 5662 5662 F DEBUG : #21 pc 0000000000075da8 /system/lib64/libc.so (_ZL15__pthread_startPv+204)
08-21 07:55:41.448 5662 5662 F DEBUG : #22 pc 000000000001e1c4 /system/lib64/libc.so (__start_thread+16)
2 Replies
Same error here! Maybe it's a different cause, but my app crashes with the "signal 11 (SIGSEGV), code 2 (SEGV_ACCERR)" response too, and I absolutely don't know how to find the cause. I'm using Unity 2022.1.1.
Did you solve your problem during these years, or maybe you found a way to debug it deeply?
I have a similar crash and error, randomly in Quest1/Quest2 via Unity 2022.1
Any solutions found?CRASHVersion '2022.1.20f1 (01d83b40d570)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'12:37:26.172CRASHBuild fingerprint: 'oculus/vr_monterey/monterey:10/QQ3A.200805.001/47421700667500000:user/release-keys'12:37:26.172CRASHRevision: '0'12:37:26.172CRASHABI: 'arm64'12:37:26.172CRASHTimestamp: 2022-11-07 12:37:26-080012:37:26.172CRASHpid: 4270, tid: 4331, name: Thread-2 >>> com.SteveHinanPresents.MetalMultiball <<<12:37:26.172CRASHuid: 1010512:37:26.172CRASHsignal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x7120402000
