Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice

Constant Crash on Galaxy S3 (Verizon)

Discussion in 'Android' started by sekari, Jan 22, 2016.

  1. sekari

    sekari

    Joined:
    Jan 13, 2015
    Posts:
    27
    My customers with Galaxy S3 facing with crashes when using my application. The only log I have is from the Play Store native log and it says:

    Game built with Unity 4.6.8.p4
    Devices:
    1) Samsung SPH-L710 (Galaxy S3 for Sprint)
    2) Samsung SGH-I747 (Galaxy S3 for AT&T)
    3) Samsung SGH-I535 (Galaxy S3 for Verizon)

    *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    Build fingerprint: 'Verizon/d2vzw/d2vzw:4.4.2/KOT49H/I535VRUDNE1:user/release-keys'
    Revision: '15'
    pid: 6063, tid: 6092, name: UnityPreload >>> net.MyCompany.MyPackage <<<
    signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
    Abort message: 'heap corruption detected by dlmalloc'
    r0 00000000 r1 000017cc r2 00000006 r3 00000000
    r4 00000006 r5 00000016 r6 000017cc r7 0000010c
    r8 00000040 r9 62333c50 sl 00000000 fp 001017c0
    ip 00000010 sp 637cb9a8 lr 4005a18d pc 40069134 cpsr 000f0010
    d0 0101010101010101 d1 0101010101010101
    d2 412e848000000000 d3 0000000000000000
    d4 0000000000000000 d5 0000000000000000
    d6 0000000000000000 d7 0000000000000000
    d8 000000003f800000 d9 0000000000000000
    d10 0000000000000000 d11 0000000000000000
    d12 0000000000000000 d13 0000000000000000
    d14 0000000000000000 d15 0000000000000000
    d16 726f632070616568 d17 206e6f6974707572
    d18 0000000000000000 d19 0000000000000000
    d20 0000000000000000 d21 0000000000000000
    d22 0000000000000000 d23 0000000000000000
    d24 bf29f2e90108cd05 d25 3fc3bd3cdc2cab20
    d26 3fd87de2b1857ab1 d27 3faf019b84a612a9
    d28 3f985a2eb9a334dc d29 3ec6cd878c3b46a7
    d30 3f5798966f109e41 d31 3ef99342e0ee5069
    scr 28000013

    backtrace:
    #00 pc 00022134 /system/lib/libc.so (tgkill+12)
    #01 pc 00013189 /system/lib/libc.so (pthread_kill+48)
    #02 pc 0001339d /system/lib/libc.so (raise+10)
    #03 pc 000120d3 /system/lib/libc.so
    #04 pc 000219e8 /system/lib/libc.so (abort+4)
    #05 pc 00012bb9 /system/lib/libc.so
    #06 pc 0000f2c5 /system/lib/libc.so
    #07 pc 000101d1 /system/lib/libc.so (dlmalloc+604)
    #08 pc 000112bb /system/lib/libc.so
    #09 pc 0000dd4f /system/lib/libc.so (memalign+10)
    #10 pc 000b8fc4 /mnt/asec/net.MyCompany.MyPackage-1/lib/libunity.so
    #11 pc 000b60d4 /mnt/asec/net.MyCompany.MyPackage-1/lib/libunity.so
    #12 pc 000b5dd0 /mnt/asec/net.MyCompany.MyPackage-1/lib/libunity.so
    #13 pc 0011e6b4 /mnt/asec/net.MyCompany.MyPackage-1/lib/libunity.so
    #14 pc 000c7adc /mnt/asec/net.MyCompany.MyPackage-1/lib/libunity.so
    #15 pc 00231278 /mnt/asec/net.MyCompany.MyPackage-1/lib/libunity.so
    #16 pc 00230f58 /mnt/asec/net.MyCompany.MyPackage-1/lib/libunity.so
    #17 pc 002f6be4 /mnt/asec/net.MyCompany.MyPackage-1/lib/libunity.so
    #18 pc 002f7dac /mnt/asec/net.MyCompany.MyPackage-1/lib/libunity.so
    #19 pc 002a2954 /mnt/asec/net.MyCompany.MyPackage-1/lib/libunity.so
    #20 pc 002a23bc /mnt/asec/net.MyCompany.MyPackage-1/lib/libunity.so
    #21 pc 002a2170 /mnt/asec/net.MyCompany.MyPackage-1/lib/libunity.so
    #22 pc 00319a58 /mnt/asec/net.MyCompany.MyPackage-1/lib/libunity.so
    #23 pc 0000d278 /system/lib/libc.so (__thread_entry+72)
    #24 pc 0000d410 /system/lib/libc.so (pthread_create+240)

    Another one here - similar issue:

    Build fingerprint: 'samsung/d2ltetmo/d2ltetmo:4.3/JSS15J/T999LUVUBOH1:user/release-keys'
    Revision: '16'
    pid: 27522, tid: 27536, name: asyncProcessor >>> net.MyCompany.MyPackage <<<
    signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
    Abort message: '@@@ ABORTING: invalid address or address of corrupt block 0x66380038 passed to dlfree'
    r0 00000027 r1 00000000 r2 00000000 r3 deadbaad
    r4 00000000 r5 5feb99fc r6 4001f000 r7 66380040
    r8 001017c0 r9 5fc49a00 sl 5fc49124 fp 5fd635b4
    ip 66380040 sp 5feb99f8 lr 40055497 pc 400529b8 cpsr 60000030
    d0 524f424120404040 d1 6e69203a474e4954
    d2 64612064696c6176 d3 726f207373657264
    d4 772bfd614b7737a7 d5 66112fc404b48d20
    d6 3e6a39d72a18f5ce d7 8ce5a7b9a467a388
    d8 0000000000000000 d9 0000000000000000
    d10 0000000000000000 d11 0000000000000000
    d12 0000000000000000 d13 0000000000000000
    d14 0000000000000000 d15 0000000000000000
    d16 7373657264646120 d17 72726f6320666f20
    d18 d911b076fb06bb35 d19 7e72c6ef55a7b248
    d20 481a29aa62686377 d21 257683245a6527b2
    d22 b2447dc39c90e78d d23 a3a52a8c0fd0cd27
    d24 3fc74721cad6b0ed d25 3fc2f112df3e5244
    d26 40026bb1bbb55516 d27 4000000000000000
    d28 40008df2d49d41f1 d29 3fb0f4a31edab38b
    d30 3ff0000000000000 d31 3f4de16b9c24a98f
    scr 80000010

    Another One Here:

    java.lang.Error: FATAL EXCEPTION [UnityMain]
    Unity version : 4.6.8p4
    Device model : samsung SPH-L710
    Device fingerprint: samsung/d2spr/d2spr:4.4.2/KOT49H/L710VPUDOH1:user/release-keys

    Caused by: java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 69c479d8
    Build fingerprint: 'samsung/d2spr/d2spr:4.4.2/KOT49H/L710VPUDOH1:user/release-keys'
    Revision: '14'
    pid: 24400, tid: 24415, name: main >>> net.MyCompany.MyPackage <<<
    r0 69c479d8 r1 69c48000 r2 fffffe5c r3 69c48000
    r4 69c479d8 r5 00000001 r6 69c47ffc r7 7b2af0cc
    r8 62ce6b34 r9 5c647f60 sl 5c642ec8 fp 6272090c
    ip 618fced4 sp 627208e0 lr 618185f4 pc 61818564 cpsr 55505630

    at libmono.002c9564(Native Method)
    at libmono.GC_push_all_stack(GC_push_all_stack:72)
    at libmono.002d4c0c(Native Method)
    at libmono.002d4cdc(Native Method)
    at libmono.002ced58(Native Method)
    at libmono.002cb368(Native Method)
    at libmono.002c793c(Native Method)
    at libmono.002bd8b4(Native Method)
    at libmono.002bd2f8(Native Method)
    at libmono.002be15c(Native Method)
    at libmono.002be1fc(Native Method)
    at libmono.mono_gc_collect(mono_gc_collect:40)
    at libmono.mono_domain_finalize(mono_domain_finalize:96)
    at libmono.00026ad8(Native Method)
    at libmono.mono_jit_cleanup(mono_jit_cleanup:20)
    at libunity.00208ed4(Native Method)
    at libunity.0029f9e8(Native Method)
    at libunity.003d3e3c(Native Method)
    at libunity.003df0c0(Native Method)
    at libdvm.dvmPlatformInvoke(dvmPlatformInvoke:112)
    at libdvm.dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)(dvmCallJNIMethod:398)
    at libdvm.0002a220(Native Method)
    at libdvm.dvmMterpStd(Thread*)(dvmMterpStd:76)
    at libdvm.dvmInterpret(Thread*, Method const*, JValue*)(dvmInterpret:184)
    at libdvm.dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)(dvmCallMethodV:336)
    at libdvm.dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)(dvmCallMethod:20)
    at libdvm.00058d2b(Native Method)
    at libc.__thread_entry(__thread_entry:72)
    at libc.pthread_create(pthread_create:240)
     
    Last edited: Jan 22, 2016
  2. Marzoa

    Marzoa

    Joined:
    Dec 2, 2012
    Posts:
    50
    I have the very same problem with several devices of my users, as reported remotely by Crittercism, although I haven't been able to reproduce it on my own so far.

    Here's my stack trace:

    0 java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 9df599d0
    1 Build fingerprint: 'htc/a32eul_aio_wireless_us/htc_a32eul:5.1/LMY47O/648333.6:user/release-keys'
    2 Revision: '0'
    3 pid: 30399, tid: 30421, name: main >>> com.whatever.thehell <<<
    4 r0 9df599d0 r1 9df5a000 r2 fffffe5c r3 9df5a000
    5 r4 9df599d0 r5 00000001 r6 9df59ffc r7 a2968f74
    6 r8 9989a08c r9 b7ddb038 sl 00000000 fp a0c88cac
    7 ip a1d38ed4 sp a0c88c80 lr a1c545f4 pc a1c54564 cpsr 2e353a6c
    8
    9 at libmono.002c9564(Native Method)
    10 at libmono.GC_push_all_stack(GC_push_all_stack:72)
    11 at libmono.002d4c0c(Native Method)
    12 at libmono.002d4cdc(Native Method)
    13 at libmono.002ced58(Native Method)
    14 at libmono.002cb368(Native Method)
    15 at libmono.002c793c(Native Method)
    16 at libmono.002bd8b4(Native Method)
    17 at libmono.002bd2f8(Native Method)
    18 at libmono.002be15c(Native Method)
    19 at libmono.002be1fc(Native Method)
    20 at libmono.mono_gc_collect(mono_gc_collect:40)
    21 at libmono.mono_domain_finalize(mono_domain_finalize:96)
    22 at libmono.00026ad8(Native Method)
    23 at libmono.mono_jit_cleanup(mono_jit_cleanup:20)
    24 at libunity.00208ed4(Native Method)
    25 at libunity.0029f9e8(Native Method)
    26 at libunity.003d3e3c(Native Method)
    27 at libunity.003df0c0(Native Method)
    28 at data@app@com.0000060f(Native Method)
     
  3. sekari

    sekari

    Joined:
    Jan 13, 2015
    Posts:
    27
    @Marzoa What is your Unity version?
     
    JamesArndt likes this.
  4. Marzoa

    Marzoa

    Joined:
    Dec 2, 2012
    Posts:
    50
    This have been happening with both, the last 4.6.x and 4.7, at least.