Forum Discussion
TheBiggestBob
2 years agoHonored Guest
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?
1 Reply
Replies have been turned off for this discussion
- tylercroachProtege
I'm getting a Sigabrt Signal 6 error Code -1. Let me know if you were able to fix your issue. I believe it has something to do with Oculus firmware 50 and Android 12. They have completely broken our metaverse and we have tried everything so far. Apparently even if it did run performance would be much slower. We did find that using Mono with Arm7 worked but only with 4 scenes or so. On latest Oculus SDK as well.
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 3 years ago
- 12 years ago