SIGSEGV crash on startup on Android with Unity 5.5.0f3

Hey,

We’re building our app with Unity 5.5.0f3 and getting a SIGSEGV crash on startup. The crash happens when booting up the app once or twice, and then it correctly boots up. I have absolutely no clue what’s the cause of this. I’ve tried making release builds. Debug builds. FAT and arm only builds. Tried building with il2cpp but that didn’t make it onto the device because of errors.

Does anyone have any ideas?

Cheers,

Paul

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 10.0px Monaco; color: #f5f5f5; background-color: #000000} span.s1 {font-variant-ligatures: no-common-ligatures}

01-18 20:20:35.841 3057 3057 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

01-18 20:20:35.841 3057 3057 F DEBUG : Build fingerprint: ‘samsung/zerofltedv/zeroflte:6.0.1/MMB29K/G920IDVS3EPK1:user/release-keys’

01-18 20:20:35.841 3057 3057 F DEBUG : Revision: ‘11’

01-18 20:20:35.841 3057 3057 F DEBUG : ABI: ‘arm’

01-18 20:20:35.841 3057 3057 F DEBUG : pid: 28023, tid: 28039, name: UnityMain >>> co.dpt.theenemy <<<

01-18 20:20:35.841 3057 3057 F DEBUG : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x13213000

01-18 20:20:35.901 3057 3057 F DEBUG : r0 0039acaa r1 12c5a828 r2 00000000 r3 13213000

01-18 20:20:35.901 3057 3057 F DEBUG : r4 12c5a827 r5 00002800 r6 13213000 r7 ee9bee68

01-18 20:20:35.901 3057 3057 F DEBUG : r8 f48fde78 r9 f499a928 sl 12e71080 fp ee9bee6c

01-18 20:20:35.901 3057 3057 F DEBUG : ip 00002800 sp ee9bee2c lr f4711751 pc f480451c cpsr 20070030

01-18 20:20:35.901 3057 3057 F DEBUG :

01-18 20:20:35.901 3057 3057 F DEBUG : backtrace:

01-18 20:20:35.901 3057 3057 F DEBUG : #00 pc 0036e51c /system/lib/libart.so (_ZN3art14CountUtf8BytesEPKtj+15)

01-18 20:20:35.901 3057 3057 F DEBUG : #01 pc 0027b74d /system/lib/libart.so (_ZN3art3JNI17GetStringUTFCharsEP7_JNIEnvP8_jstringPh+344)

01-18 20:20:35.901 3057 3057 F DEBUG : #02 pc 0099ca88 /data/app/co.dpt.theenemy-1/lib/arm/libunity.so

01-18 20:20:36.281 3489 4464 D libgps : OnGpsExtensionMessage: message_id(1), data(0x7f8a98b444), size(2432)

01-18 20:20:36.281 3489 4464 D libgps : GpsiHook: API: gpsSvStatusCb(GpsiHookStateGps: e,c,g)

01-18 20:20:36.281 3489 4464 D libgps : proxy__gps_sv_status_cb : called

01-18 20:20:36.351 3489 28179 W ActivityManager: Force finishing activity co.dpt.theenemy/com.google.unity.GoogleUnityActivity

01-18 20:20:36.351 3057 3057 F DEBUG :

01-18 20:20:36.351 3057 3057 F DEBUG : Tombstone written to: /data/tombstones/tombstone_06

01-18 20:20:36.351 3057 3057 E DEBUG : AM write failed: Broken pipe

Hard to tell from just this output, but it appears that you may have a plugin/library that is trying to initialize the GPS? Maybe the GPS library does not initialize immediately, so you might want to check when you try to access its functionality.

After having done some research it seems like Google VR being built with Unity 5.5 that is causing the crash. Several people on the GVR forums have the same problem.

FYI: I do not use Google VR and I have the same issue since upgrading to Unity 5.5

--------- beginning of crash
01-27 22:40:19.938 24665-24680/? A/libc: Fatal signal 11 (SIGSEGV), code 2, fault addr 0x12f9c000 in tid 24680 (main)

[ 01-27 22:40:19.938 557: 557 W/ ]
debuggerd: handling request: pid=24665 uid=10304 gid=10304 tid=24680
01-27 22:40:19.943 24230-24246/? D/[ACT]:ao: processing priority = HIGH
01-27 22:40:19.946 24248-24264/? D/[ACT]:ao: processing priority = HIGH
01-27 22:40:19.953 24925-24925/? W/debuggerd: type=1400 audit(0.0:6410): avc: denied { search } for name=“de.lications.tnbrtrm.aibattleship” dev=“sda35” ino=2236489 scontext=u:r:debuggerd:s0 tcontext=u:object_r:app_data_file:s0:c512,c768 tclass=dir permissive=0
01-27 22:40:20.020 24925-24925/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-27 22:40:20.020 24925-24925/? A/DEBUG: Build fingerprint: ‘google/marlin/marlin:7.1.1/NMF26U/3562008:user/release-keys’
01-27 22:40:20.020 24925-24925/? A/DEBUG: Revision: ‘0’
01-27 22:40:20.021 24925-24925/? A/DEBUG: ABI: ‘arm’
01-27 22:40:20.021 24925-24925/? A/DEBUG: pid: 24665, tid: 24680, name: main >>> de.lications.tnbrtrm.aibattleship <<<
01-27 22:40:20.022 24925-24925/? A/DEBUG: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x12f9c000
01-27 22:40:20.022 24925-24925/? A/DEBUG: r0 002923a5 r1 00000000 r2 12f9c000 r3 12f9c000
01-27 22:40:20.022 24925-24925/? A/DEBUG: r4 0000ffff r5 12d16a18 r6 00000b7e r7 eaf2f668
01-27 22:40:20.022 24925-24925/? A/DEBUG: r8 00000043 r9 eaf7eef0 sl eaf30269 fp eaf3029a
01-27 22:40:20.022 24925-24925/? A/DEBUG: ip 00000000 sp e9b68740 lr 3859f858 pc eae5d5d2 cpsr 800d0030
01-27 22:40:20.036 24925-24925/? A/DEBUG: backtrace:
01-27 22:40:20.036 24925-24925/? A/DEBUG: #00 pc 0034c5d2 /system/lib/libart.so (_ZN3art14CountUtf8BytesEPKtj+67)
01-27 22:40:20.036 24925-24925/? A/DEBUG: #01 pc 0027d33b /system/lib/libart.so (_ZN3art3JNI17GetStringUTFCharsEP7_JNIEnvP8_jstringPh+430)
01-27 22:40:20.037 24925-24925/? A/DEBUG: #02 pc 0099ca88 /data/app/de.lications.tnbrtrm.aibattleship-1/lib/arm/libunity.so
01-27 22:40:20.319 1119-1722/? E/LocSvc_eng: E/Calling gnss_sv_status_cb
01-27 22:40:21.046 1119-24926/? W/ActivityManager: Force finishing activity de.lications.tnbrtrm.aibattleship/com.unity3d.player.UnityPlayerActivity

@Rainking , do you use location services in the project? There is a fix for a similar crash in the 5.5.1p3(EDIT:5.5.1p4, sorry for mistake!), please let me know how it works, especially if it crashes :wink:

tagging @pgeorges-dpt as well

Got the same crash in my project.
The 5.5.1p3 did not fixed this (And I do not see the related fix in the change log).

It does not crash anymore when disabling the Location service,
Which seems to indicate that this is the right problem, but is the fix really present in the 5.5.1p3 ?

@Jonas_Sid do you have a link to this issue ?

@WillFvrther , sorry it seems I made a mistake. It’s gonna be in 5.5.1p4.

@Jonas_Sid , yes I used location services and found out a bit later that this was the root cause. Currently, I do not use this code part. I’ll try the patch soon, thank you! When will be p4 released?