"signal 11 (SIGSEGV), code 2 (SEGV_ACCERR)" (750311)

Unity Engine
,
1

I built a ARM64 apk in Unity 2017.4.30f1, and it crashes sometimes with the same error

07-05 15:48:43.628 13221 13250 E CRASH   : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 00000076a82b4778
07-05 15:48:43.628 13221 13250 E CRASH   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-05 15:48:43.628 13221 13250 E CRASH   : Build fingerprint: 'google/sailfish/sailfish:9/PQ1A.181205.002.A1/5129870:user/release-keys'
07-05 15:48:43.628 13221 13250 E CRASH   : Revision: '0'
07-05 15:48:43.628 13221 13250 E CRASH   : pid: 13221, tid: 13250, name: UnityMain  >>> com.bbtus.ltd <<<
07-05 15:48:43.628 13221 13250 E CRASH   :     x0   fff9000000000000  x1   8000000000000000  x2   0000000000000003  x3   00000076c0b97520
07-05 15:48:43.628 13221 13250 E CRASH   :     x4   fffffffffffffffb  x5   fff9000000000000  x6   00000076a7c2d980  x7   0000000000000000
07-05 15:48:43.628 13221 13250 E CRASH   :     x8   00000076abab7d4c  x9   00000076aba8c640  x10  00000076abab7db0  x11  00000076abab7dd4
07-05 15:48:43.628 13221 13250 E CRASH   :     x12  00000076abab7bd0  x13  00000076abab7bec  x14  00000000b9406fe0  x15  00000076b6184050
07-05 15:48:43.628 13221 13250 E CRASH   :     x16  00000000004f0854  x17  000000775101eb30  x18  00000076b6184020  x19  00000076b7501330
07-05 15:48:43.628 13221 13250 E CRASH   :     x20  0000000000000000  x21  00000076b7501370  x22  00000076c4c013d8  x23  fffffffffffffffb
07-05 15:48:43.628 13221 13250 E CRASH   :     x24  00000076a7c2d920  x25  00000076c23048b8  x26  0000000000000004  x27  0000000000000005
07-05 15:48:43.628 13221 13250 E CRASH   :     x28  0000000000000005  x29  00000076b6184710  x30  fff9000000000004
07-05 15:48:43.628 13221 13250 E CRASH   :     sp   00000076b61846e0  pc   00000076a82b4778  pstate 0000000060000000
07-05 15:48:43.628 13221 13250 E CRASH   :
07-05 15:48:43.628 13221 13250 E CRASH   : backtrace:
07-05 15:48:43.628 13221 13250 E CRASH   :     #00  pc 000000000033c26c  /data/app/com.bbtus.ltd-FKjcYMuBnhkYUAyH1a7DaQ==/lib/arm64/libunity.so
07-05 15:48:43.628 13221 13250 E CRASH   :     #01  pc 00000000003606d4  /data/app/com.bbtus.ltd-FKjcYMuBnhkYUAyH1a7DaQ==/lib/arm64/libunity.so
07-05 15:48:43.628 13221 13250 E CRASH   :     #02  pc 0000000000002a90  /system/bin/app_process64
07-05 15:48:43.628 13221 13250 E CRASH   :     #03  pc 0000000000000870  [vdso] (__kernel_rt_sigreturn)
07-05 15:48:43.628 13221 13250 E CRASH   :     #04  pc 00000076a82b4778  <unknown/absolute>
07-05 15:48:43.629 13221 13250 E MessageQueue: IdleHandler threw exception
07-05 15:48:43.629 13221 13250 E MessageQueue: java.lang.Error: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 00000076a82b4778
07-05 15:48:43.629 13221 13250 E MessageQueue: Build fingerprint: 'google/sailfish/sailfish:9/PQ1A.181205.002.A1/5129870:user/release-keys'
07-05 15:48:43.629 13221 13250 E MessageQueue: Revision: '0'
07-05 15:48:43.629 13221 13250 E MessageQueue: pid: 13221, tid: 13250, name: UnityMain  >>> com.bbtus.ltd <<<
07-05 15:48:43.629 13221 13250 E MessageQueue:     x0   fff9000000000000  x1   8000000000000000  x2   0000000000000003  x3   00000076c0b97520
07-05 15:48:43.629 13221 13250 E MessageQueue:     x4   fffffffffffffffb  x5   fff9000000000000  x6   00000076a7c2d980  x7   0000000000000000
07-05 15:48:43.629 13221 13250 E MessageQueue:     x8   00000076abab7d4c  x9   00000076aba8c640  x10  00000076abab7db0  x11  00000076abab7dd4
07-05 15:48:43.629 13221 13250 E MessageQueue:     x12  00000076abab7bd0  x13  00000076abab7bec  x14  00000000b9406fe0  x15  00000076b6184050
07-05 15:48:43.629 13221 13250 E MessageQueue:     x16  00000000004f0854  x17  000000775101eb30  x18  00000076b6184020  x19  00000076b7501330
07-05 15:48:43.629 13221 13250 E MessageQueue:     x20  0000000000000000  x21  00000076b7501370  x22  00000076c4c013d8  x23  fffffffffffffffb
07-05 15:48:43.629 13221 13250 E MessageQueue:     x24  00000076a7c2d920  x25  00000076c23048b8  x26  0000000000000004  x27  0000000000000005
07-05 15:48:43.629 13221 13250 E MessageQueue:     x28  0000000000000005  x29  00000076b6184710  x30  fff9000000000004
07-05 15:48:43.629 13221 13250 E MessageQueue:     sp   00000076b61846e0  pc   00000076a82b4778  pstate 0000000060000000
07-05 15:48:43.629 13221 13250 E MessageQueue:
07-05 15:48:43.629 13221 13250 E MessageQueue:     at libunity.0033c26c(Native Method)
07-05 15:48:43.629 13221 13250 E MessageQueue:     at libunity.003606d4(Native Method)
07-05 15:48:43.629 13221 13250 E MessageQueue:     at app_process64.00002a90(Native Method)
07-05 15:48:43.629 13221 13250 E MessageQueue:     at [vdso].__kernel_rt_sigreturn(__kernel_rt_sigreturn:0)
07-05 15:48:43.629 13221 13250 E MessageQueue:     at Unknown.a82b4778(Unknown Source:0)
2

You can use unity2018.4.30f1.

3

Got same problem in 2018.4.4f1, maybe that’s Android problem?

4

Got same problem in HuaWei Android 8.x,

5

You can use libunity symbol table location problem.

6

Should be unity bug.You should be bypass some unity api.

7

Unity符号表 - 何文西 - 博客园 to help you

8

cool, thank you very much, I’ll take a look

9

I ran addr2line to see Android symbols but seems can’t find anything helpful

unwind_backtrace_signal_arch(siginfo*, void*, map_info const*, backtrace_frame_t*, unsigned long, unsigned long)
??:?
NativeRuntimeException::signal_handler(int, siginfo*, void*)
??:?
10

and I built my project in 2018.4.5f1 an hour ago but can’t get backtrack anymore, even in debug mode

07-29 15:01:53.497 13346 13378 E CRASH   : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 000000776a01103c
07-29 15:01:53.497 13346 13378 E CRASH   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-29 15:01:53.497 13346 13378 E CRASH   : Build type 'Development', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
07-29 15:01:53.497 13346 13378 E CRASH   : Build fingerprint: 'google/sailfish/sailfish:9/PQ3A.190705.001/5565753:user/release-keys'
07-29 15:01:53.497 13346 13378 E CRASH   : Revision: '0'
07-29 15:01:53.497 13346 13378 E CRASH   : pid: 13346, tid: 13378, name: UnityMain  >>> com.bbt <<<
07-29 15:01:53.497 13346 13378 E CRASH   :     x0   000000778387a378  x1   000000776bc95a80  x2   fffd80776bc27e38  x3   0000007766070000
07-29 15:01:53.497 13346 13378 E CRASH   :     x4   fffd80776bc7b2e0  x5   fffd807772e5bf78  x6   fffd80778387cc18  x7   00000000f48f3f5d
07-29 15:01:53.497 13346 13378 E CRASH   :     x8   fffd80777b0d8fb0  x9   00000000d83f70cb  x10  fffd807772eb2ab8  x11  fffd80778387df98
07-29 15:01:53.497 13346 13378 E CRASH   :     x12  fffd80777b0d8fb0  x13  00000000d83f70cb  x14  fffd80778387cc18  x15  000000776da18740
07-29 15:01:53.497 13346 13378 E CRASH   :     x16  000000776d6b09d0  x17  0000000000000000  x18  00000000ffffffff  x19  000000776d67d530
07-29 15:01:53.497 13346 13378 E CRASH   :     x20  0000000000000000  x21  000000776bc82920  x22  000000778387a3d8  x23  000000778387df60
07-29 15:01:53.497 13346 13378 E CRASH   :     x24  000000776bc828f0  x25  000000778387df60  x26  0000007772e59be8  x27  0000007766075b28
07-29 15:01:53.497 13346 13378 E CRASH   :     x28  000000776da184d8  x29  000000777a1ccfd0  x30  fffd80778387cc18
07-29 15:01:53.497 13346 13378 E CRASH   :     sp   000000777a1ccfb0  pc   000000776a01103c  pstate 0000000020000000
07-29 15:01:53.497 13346 13378 E CRASH   :
07-29 15:01:53.497 13346 13378 E CRASH   : backtrace:
11

Hello
I am struggling with the same issue. Error files are attached. I have two different apps and I am testing on a Nexus5X with Android 8.1. This issue currently only occures on this particular device. On modern device it runs well.

I tried different build combinations, some worked others dont. I am trying to get a working version from unity cloud build.
Also split apk does not help. Any ideas? Is it because of an old device? Any help is welcome.

Here are the logs: Important! From different Apps.

4801424–459113–Error1.txt (74.7 KB)
4801424–459116–Error2.txt (10.4 KB)

12

update: seems my error has been solved. I used a plugin named “tolua”, it’s there error, I updated it to the latest version and no crash anymore

13

Hello
I’ve had the same problem, but the same error still happens after updating “tolua”.
Can you tell me the address of the latest version of “tolua” which you updated?