Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

E/CRASH(7870): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000007c2f6

Discussion in 'Editor & General Support' started by Flarvain, Sep 20, 2019.

  1. Flarvain

    Flarvain

    Joined:
    Mar 27, 2017
    Posts:
    13
    Hi All,

    I've been having troubles recently with my apps in alpha on the play store. I have been doing a bit of work recently and just using the Run and Build option inside of Unity to test that my application is working correctly however, i've been a bit stumped with this issue.

    When i attempt to download my app off the playstore (Closed Alpha) the application seems to install without any issues but the moment it opens it immediately closes.

    I've hooked up my phone to my pc and run the adb logcat in cmd as well as the monitor from tools and i get the following crash when i attempt to open it:

    i've edited my fingerprint and company name

    09-21 07:42:05.103: E/CRASH(7870): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000007c2f67f818
    09-21 07:42:05.103: E/CRASH(7870): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    09-21 07:42:05.103: E/CRASH(7870): Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
    09-21 07:42:05.103: E/CRASH(7870): Build fingerprint: 'OnePlus/OnePlus3/OnePlus3T:9/***********/**********:user/release-keys'
    09-21 07:42:05.103: E/CRASH(7870): Revision: '0'
    09-21 07:42:05.104: E/CRASH(7870): pid: 7870, tid: 9955, name: UnityMain >>> com.Company.Game <<<
    09-21 07:42:05.104: E/CRASH(7870): x0 00000079ff9c67d8 x1 0000000000000007 x2 0000007a9e1ec560 x3 0000000000cdb330
    09-21 07:42:05.104: E/CRASH(7870): x4 00000000001c8b08 x5 0000000000ce3330 x6 00000000001ccb08 x7 e661aa1c417c1492
    09-21 07:42:05.104: E/CRASH(7870): x8 00000000464c457f x9 00000079fd05cc20 x10 0000000000539a10 x11 00000000000000e4
    09-21 07:42:05.104: E/CRASH(7870): x12 e661aa1c417c1492 x13 00000000000000d5 x14 00000000000000d5 x15 0000007a9e1a8cc0
    09-21 07:42:05.104: E/CRASH(7870): x16 0000007a9e1e31e0 x17 0000007a9e0e34b8 x18 0000000000000004 x19 00000079ff7fcdb0
    09-21 07:42:05.104: E/CRASH(7870): x20 00000079fb84e6d8 x21 00000079fd283000 x22 00000079fd023530 x23 00000079fd283000
    09-21 07:42:05.104: E/CRASH(7870): x24 00000079fd283000 x25 00000079fd283000 x26 00000000000002d4 x27 00000079fb84e6d4
    09-21 07:42:05.104: E/CRASH(7870): x28 0000000000000ae5 x29 00000079ff7fce30 x30 00000079fbef29f4
    09-21 07:42:05.104: E/CRASH(7870): sp 00000079ff7fcda0 pc 00000079fbef29e0 pstate 0000000000000000


    09-21 07:42:05.104: E/CRASH(7870): backtrace:
    09-21 07:42:34.377: E/CRASH(9993): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000007c2f76e818
    09-21 07:42:34.377: E/CRASH(9993): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    09-21 07:42:34.377: E/CRASH(9993): Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
    09-21 07:42:34.377: E/CRASH(9993): Build fingerprint: 'OnePlus/OnePlus3/OnePlus3T:9/**********/*********:user/release-keys'
    09-21 07:42:34.377: E/CRASH(9993): Revision: '0'
    09-21 07:42:34.377: E/CRASH(9993): pid: 9993, tid: 10035, name: UnityMain >>> com.Company.Game <<<
    09-21 07:42:34.377: E/CRASH(9993): x0 00000079ff9ec7d8 x1 0000000000000007 x2 0000007a9e1ec560 x3 0000000000cda6a0
    09-21 07:42:34.377: E/CRASH(9993): x4 00000000001c7748 x5 0000000000ce26a0 x6 00000000001cb748 x7 e661aa1c417c1492
    09-21 07:42:34.377: E/CRASH(9993): x8 00000000464c457f x9 00000079fd14bc20 x10 0000000000539a10 x11 00000000000000e4
    09-21 07:42:34.377: E/CRASH(9993): x12 e661aa1c417c1492 x13 00000000000000d8 x14 00000000000000d8 x15 0000007a9e1a8cc0
    09-21 07:42:34.377: E/CRASH(9993): x16 0000007a9e1e31e0 x17 0000007a9e0e34b8 x18 0000000000000004 x19 00000079ff7fcdb0
    09-21 07:42:34.377: E/CRASH(9993): x20 00000079fb93d6d8 x21 00000079fd372000 x22 00000079fd112530 x23 00000079fd372000
    09-21 07:42:34.377: E/CRASH(9993): x24 00000079fd372000 x25 00000079fd372000 x26 00000000000002d4 x27 00000079fb93d6d4
    09-21 07:42:34.377: E/CRASH(9993): x28 0000000000000ae5 x29 00000079ff7fce30 x30 00000079fbfe19f4
    09-21 07:42:34.377: E/CRASH(9993): sp 00000079ff7fcda0 pc 00000079fbfe19e0 pstate 0000000000000000
    09-21 07:42:34.377: E/CRASH(9993): backtrace:
    09-21 07:42:34.403: E/CRASH(9993): #00 pc 000000000000068c [vdso] ()
    09-21 07:42:34.403: E/CRASH(9993): #01 pc 00000000006a19dc /data/app/com.Company.Game-lZRPnhDcySTa8I_G8bddEg==/split_config.arm64_v8a.apk ()
    09-21 07:42:34.403: E/CRASH(9993): #02 pc 00000000006a157c /data/app/com.Company.Game-lZRPnhDcySTa8I_G8bddEg==/split_config.arm64_v8a.apk ()
    09-21 07:42:34.403: E/CRASH(9993): #03 pc 00000000006a9680 /data/app/com.Company.Game-lZRPnhDcySTa8I_G8bddEg==/split_config.arm64_v8a.apk ()
    09-21 07:42:34.404: E/CRASH(9993): #04 pc 0000000000676d8c /data/app/com.Company.Game-lZRPnhDcySTa8I_G8bddEg==/split_config.arm64_v8a.apk ()
    09-21 07:42:34.404: E/CRASH(9993): #05 pc 00000000003386bc /data/app/com.Company.Game-lZRPnhDcySTa8I_G8bddEg==/split_config.arm64_v8a.apk ()
    09-21 07:42:34.404: E/CRASH(9993): #06 pc 00000000002da0a0 /data/app/com.Company.Game-lZRPnhDcySTa8I_G8bddEg==/split_config.arm64_v8a.apk ()
    09-21 07:42:34.404: E/CRASH(9993): #07 pc 00000000002da9b4 /data/app/com.Company.Game-lZRPnhDcySTa8I_G8bddEg==/split_config.arm64_v8a.apk ()
    09-21 07:42:34.404: E/CRASH(9993): #08 pc 00000000002d3b1c /data/app/com.Company.Game-lZRPnhDcySTa8I_G8bddEg==/split_config.arm64_v8a.apk ()
    09-21 07:42:34.404: E/CRASH(9993): #09 pc 0000000000000d7c /data/app/com.Company.Game-lZRPnhDcySTa8I_G8bddEg==/oat/arm64/base.odex ()



    Info logs with Unity Tag on it:

    09-21 08:11:40.322: I/Unity(15669): SystemInfo CPU = ARM64 FP ASIMD AES, Cores = 4, Memory = 5738mb
    09-21 08:11:40.322: I/Unity(15669): SystemInfo ARM big.LITTLE configuration: 2 big (mask: 0xc), 2 little (mask: 0x3)
    09-21 08:11:40.322: I/Unity(15669): ApplicationInfo com.Company.Game version 0.11 build b6058604-4beb-45ab-81d6-13bed6aa8d13
    09-21 08:11:40.322: I/Unity(15669): Built from '2019.2/staging' branch, Version '2019.2.0f1 (20c1667945cf)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a', Stripping 'Enabled'



    i've been doing some reading on this and one of the recommended fixes was in this thread:
    https://issuetracker.unity3d.com/issues/android-crash-fatal-signal-11-sigsegv-on-some-devices

    which suggests that you turn off stripping and enable debug mode on the C++ Compiler Configuration.

    After re-building and placing on the app store i then get a new error:



    09-21 08:11:40.469: E/CRASH(15669): signal 6 (SIGABRT), code -6 (?), fault addr --------
    09-21 08:11:40.469: E/CRASH(15669): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    09-21 08:11:40.469: E/CRASH(15669): Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
    09-21 08:11:40.469: E/CRASH(15669): Build fingerprint: 'OnePlus/OnePlus3/OnePlus3T:9/*********/**********:user/release-keys'
    09-21 08:11:40.469: E/CRASH(15669): Revision: '0'
    09-21 08:11:40.469: E/CRASH(15669): pid: 15669, tid: 15688, name: UnityMain >>> com.Company.Game <<<
    09-21 08:11:40.469: E/CRASH(15669): x0 0000000000000000 x1 0000000000003d48 x2 0000000000000006 x3 0000000000000008
    09-21 08:11:40.469: E/CRASH(15669): x4 0000000000000080 x5 0000000000000080 x6 0000000000000080 x7 0000000000000040
    09-21 08:11:40.469: E/CRASH(15669): x8 0000000000000083 x9 e661aa1c417c1492 x10 fffffff87ffffbdf x11 e661aa1c417c1492
    09-21 08:11:40.469: E/CRASH(15669): x12 e661aa1c417c1492 x13 fffffff87ffffbdf x14 000000005d854e9c x15 0000000000000008
    09-21 08:11:40.469: E/CRASH(15669): x16 0000007a9e1e32b0 x17 0000007a9e0f5088 x18 e661aa1c417c1492 x19 0000000000003d35
    09-21 08:11:40.469: E/CRASH(15669): x20 0000000000003d48 x21 0000000000000083 x22 00000079ff3fd978 x23 00000079ff3ff588
    09-21 08:11:40.469: E/CRASH(15669): x24 00000079ff3ff588 x25 00000079ff3fd970 x26 0000007a0078d001 x27 0000007a007240b8
    09-21 08:11:40.469: E/CRASH(15669): x28 00000079ff3fd420 x29 00000079ff3fcbc0 x30 0000007a9e0e64d0
    09-21 08:11:40.469: E/CRASH(15669): sp 00000079ff3fcb80 pc 0000007a9e0e64f0 pstate 0000000060000000
    09-21 08:11:40.469: E/CRASH(15669): backtrace:
    09-21 08:11:40.495: E/CRASH(15669): #00 pc 000000000000068c [vdso] ()
    09-21 08:11:40.495: E/CRASH(15669): #01 pc 00000000000224ec /system/lib64/libc.so (abort+108)
    09-21 08:11:40.495: E/CRASH(15669): #02 pc 0000000000022874 /system/lib64/libc.so (__assert2+52)
    09-21 08:11:40.495: E/CRASH(15669): #03 pc 0000000000b073d8 /data/app/com.Company.Game-MboFrn89773Nfmb54RA7zA==/split_config.arm64_v8a.apk ()
    09-21 08:11:40.495: E/CRASH(15669): #04 pc 0000000000b150ac /data/app/com.Company.Game-MboFrn89773Nfmb54RA7zA==/split_config.arm64_v8a.apk ()
    09-21 08:11:40.495: E/CRASH(15669): #05 pc 0000000000b14a08 /data/app/com.Company.Game-MboFrn89773Nfmb54RA7zA==/split_config.arm64_v8a.apk ()
    09-21 08:11:40.495: E/CRASH(15669): #06 pc 0000000000b26474 /data/app/com.Company.Game-MboFrn89773Nfmb54RA7zA==/split_config.arm64_v8a.apk ()
    09-21 08:11:40.495: E/CRASH(15669): #07 pc 0000000000aad424 /data/app/com.Company.Game-MboFrn89773Nfmb54RA7zA==/split_config.arm64_v8a.apk ()
    09-21 08:11:40.495: E/CRASH(15669): #08 pc 0000000000654c94 /data/app/com.Company.Game-MboFrn89773Nfmb54RA7zA==/split_config.arm64_v8a.apk ()
    09-21 08:11:40.495: E/CRASH(15669): #09 pc 00000000006b5b6c /data/app/com.Company.Game-MboFrn89773Nfmb54RA7zA==/split_config.arm64_v8a.apk ()
    09-21 08:11:40.495: E/CRASH(15669): #10 pc 00000000006b64bc /data/app/com.Company.Game-MboFrn89773Nfmb54RA7zA==/split_config.arm64_v8a.apk ()
    09-21 08:11:40.495: E/CRASH(15669): #11 pc 00000000006c40d4 /data/app/com.Company.Game-MboFrn89773Nfmb54RA7zA==/split_config.arm64_v8a.apk ()
    09-21 08:11:40.495: E/CRASH(15669): #12 pc 0000000000000d7c /data/app/com.Company.Game-MboFrn89773Nfmb54RA7zA==/oat/arm64/base.odex ()



    unity Tags again:


    09-21 08:19:09.582: I/Unity(16067): SystemInfo CPU = ARM64 FP ASIMD AES, Cores = 4, Memory = 5738mb
    09-21 08:19:09.582: I/Unity(16067): SystemInfo ARM big.LITTLE configuration: 2 big (mask: 0xc), 2 little (mask: 0x3)
    09-21 08:19:09.583: I/Unity(16067): ApplicationInfo com.Company.Game version 0.12 build 8c1bcf0b-b913-4f07-be91-f94b598dbf47
    09-21 08:19:09.583: I/Unity(16067): Built from '2019.2/staging' branch, Version '2019.2.0f1 (20c1667945cf)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a', Stripping 'Disabled'



    some Info:

    • Using a OnePlus 3T
    • Using Unity 2019.2.0f1 (but had been using this for a while and it was working, no recent upgrades)
    • It runs on ARM64
    • In order to upload to the app store i have disabled x86 in my build package.
    • Causes the same issue on a different windows phone (not sure what friends phone version is, but its not a OnePlus)
    • Will break every time on open when opened from the app store
    • If i build the file as a .apk i can build, move to my phone, install and load without issue
    • build and run with APK works the same
    • build and run with AAB works the same
    • build and place on the app store, then download from there and install gives the error.


    As far as i am aware there's nothing that i have specifically changed to cause this error. I would like to resolve the original error so i'm not having to change my compiler and stripping options as it increases the file size to 44+MB instead of 20MB on the app store.

    I've been looking at this one for... a few days now, any help would be greatly appreciated :)

    Thanks
     
  2. Flarvain

    Flarvain

    Joined:
    Mar 27, 2017
    Posts:
    13
    I'm not sure if there's any else i can add to help debug this further - below is my player - other settings configuration:
    upload_2019-9-21_13-3-19.png
    upload_2019-9-21_13-3-51.png
    upload_2019-9-21_13-4-27.png

    My SDK, NDK and OpenJDK are all from the 2019.2.0f1 version directly from unity Hub:
    upload_2019-9-21_13-5-55.png

    Quite new to debugging outside of just my own code, so please let me know if there is anything i can add that will assist.

    Thanks,
     
  3. Flarvain

    Flarvain

    Joined:
    Mar 27, 2017
    Posts:
    13
    Adding to this again - I downloaded BlueStacks which allows me to play apps on my pc. when downloading the app from the playstore, i can confirm that this does work without issue - It doesn't allow you to play ads, but i think that's just a bluestacks thing.

    I also wanted to note i use GameSparks as my back end, but i'm not seeing any logs being generated there, some of the SIGSEGV issues i've found online refer to a newer version of firebase being released, but i don't use firebase.

    Thanks,
     
  4. Flarvain

    Flarvain

    Joined:
    Mar 27, 2017
    Posts:
    13
    Just bumping this one, still stuck on the same issue.

    Any help would be very appreciated!
     
  5. Flarvain

    Flarvain

    Joined:
    Mar 27, 2017
    Posts:
    13
    Bumpity Bump.

    Still not sure what i could try further on this issue.

    Cheers,
     
  6. Flarvain

    Flarvain

    Joined:
    Mar 27, 2017
    Posts:
    13
    Bump,

    Open to any ideas on what i can do to resolve this.

    Can install an APK version of my game onto my phone without issue.

    Can generate an AAB version of the game but get the error when installing on my phone after i've uploaded it to google play.

    Very stuck with this one :(
     
    Last edited: Dec 2, 2019
    DavidZobrist likes this.
  7. Flarvain

    Flarvain

    Joined:
    Mar 27, 2017
    Posts:
    13
    Alrighty,

    So after a long time of reading, it really looks like SigSev errors could be anything. I assumed it wasn't in my scripts as none of them had any errors, so I re-imported my integration scripts (unity Ads, Unity IAP). Looks like something inside of one of them was losing a reference somewhere along the line. I jumped several versions in unity Ads, (package manager going from 2.0.8 to 2.3.1), but i also updated IAP.

    I'm not sure what the cause was and i still have a getbutton error in my IAP, but I attempted publishing last night and it worked.

    Going to spend the next few days cleaning that up so its definitely fixed!

    Apologies if this doesn't really help anyone, but SigSev's really could be anything so i can't give you a this is definitely your problem kind of response.
     
    DavidZobrist likes this.
  8. tonyhan

    tonyhan

    Joined:
    Dec 29, 2015
    Posts:
    12
    try to add
    android:launchMode="singleTask" in androidmanifest.xml, in <activety>
     
  9. mcolombo

    mcolombo

    Joined:
    Sep 27, 2017
    Posts:
    16
    Hello,

    Im having a similar issue in Android.
    Specifically, it's happening when the game goes to background (touching the Home button), and after an hour or so, when resuming the game, it crashes with this error (you can see the menu of the game trying to resume and closing itself a moment later):

    java.lang.Error: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr c1f94ea0
    at split_config.

    Im using lots of packages (many firebase, facebook, google, etc).

    Unity version: 2019.2.2f1

    Did anyone encounter this problem?

    Thanks
     
  10. share_gamerz_ID

    share_gamerz_ID

    Joined:
    Mar 19, 2019
    Posts:
    12
    signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)

    split_config.arm64_v8a.apk (offset 0x2795000)

    This issue with many impacted user. AAB package.

    will try this maybe work out. and android:launchMode="singleTask" this too.
     
  11. Herkius

    Herkius

    Joined:
    Jan 9, 2014
    Posts:
    2
    I'm also finding this error in my app, but no one can reproduce it in the office. We only see it (as of now) happen in two devices in Google Play Developer Console, and it happens a lot on those two devices.

    The crash is being labeled:

    signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)

    __dl__ZNK6soinfo9is_linkedEv

    Stack trace is not helping and it's the same eveytime:

    *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    pid: 0, tid: 0 >>> [APP-PACKAGE] <<<

    backtrace:
    #00 pc 0000000000052ce4 /apex/com.android.runtime/bin/linker64 (__dl__ZNK6soinfo9is_linkedEv)
    #00 pc 000000000003b944 /apex/com.android.runtime/bin/linker64 (__dl__ZL13soinfo_unloadP6soinfo+36)
    #00 pc 000000000003d7e0 /apex/com.android.runtime/bin/linker64 (__dl__Z10do_dlclosePv+120)
    #00 pc 000000000003839c /apex/com.android.runtime/bin/linker64 (__loader_dlclose+32)
    #00 pc 000000000000108c /apex/com.android.runtime/lib64/bionic/libdl.so (dlclose+8)
    #00 pc 00000000000c1800 /data/app/[APP-PACKAGE]-p8xG7NsySqsVS3ui_HcBhw==/lib/arm64/libLWDc915IMv.so


    I'm using Firebase Analytics, Firebase RemoteConfig, IronSource SDK with some mediation adapters (Facebook Audience, AdMob and UnityAds)
     
  12. freeschool

    freeschool

    Joined:
    Dec 17, 2014
    Posts:
    9
    This sort of crash is caused by 3rd party libraries. Signal 11 is a memory violation error.
    1. Check what 3rd party libraries are used.
    2. Check if IL2CPP can support the library.
    3. If you are using an obfuscated .net library, you cannot use il2cpp.
     
    DavidZobrist likes this.
  13. Maisey

    Maisey

    Joined:
    Feb 17, 2014
    Posts:
    302
    Getting this in Unity 2017.4.40f1 as well for ~200+ devices. 85% Samsung devices and 14% Pixel devices. Did anyone find a solution?

    EDIT:
    I was able to reproduce it. It seems to do with calling Application.Quit() + Firebase. Read more here.
     
    Last edited: Jan 29, 2021
  14. Bassem102

    Bassem102

    Joined:
    Oct 11, 2017
    Posts:
    6
    I had this problem with unity 2020 what i did was uncheck "strip engine script" and check "auto graphics"
     
    vkapoor and DavidZobrist like this.
  15. zhoulei771211119

    zhoulei771211119

    Joined:
    May 24, 2022
    Posts:
    2
    Is there any other solution? I built arm7 and ARM64 aAB separately, but only ARM64 AAB flashes back
     
  16. zhoulei771211119

    zhoulei771211119

    Joined:
    May 24, 2022
    Posts:
    2
    Building arm64-only APK is normal
     
  17. sabirworkspace

    sabirworkspace

    Joined:
    Jul 19, 2023
    Posts:
    3
    Did you find the solution i have the same error.....