Crash in Resources.Load: Caused by: java.lang.Error: signal 11 (SIGSEGV), code 1 (SEG

We are seeing a number of errors such as the one below where a crash occurs that appears to be an unhandled null pointer in native Unity Java code. These errors occur for users that have played our game for 1-3 hours continuously. We have no way of determining what is causing these errors and they don't seem to be relate to any particular assets we are loading. They occur for some assets that were previously loaded just fine by these same users in the same session.

Is anyone else seeing these or have any ideas how we could determine the cause?

java.lang.Error: FATAL EXCEPTION [GLThread 4253]
Unity version : 4.2.1f4
Device model : HTC HTC One
Device fingerprint: telus_wwe/m7/m7:4.1.2/JZO54K/164689.17:user/release-keys

Caused by: java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000028
Build fingerprint: 'telus_wwe/m7/m7:4.1.2/JZO54K/164689.17:user/release-keys'
Revision: '3'
pid: 23148, tid: 23169, name: UNKNOWN >>> UNKNOWN <<<
r0 00000000 r1 4018241c r2 00000000 r3 00000001
r4 00000000 r5 00000000 r6 6bc40428 r7 6b8aefd0
r8 735fb1cc r9 004df543 sl 004df543 fp 74205f8c
ip 6b8a000c sp 6bc40398 lr 6b37ce48 pc 40152882 cpsr 0000000b

at Unknown.40152882(Unknown Source)
at Unknown.6b37ce44(Unknown Source)
at Resources.Load(Native Method)
at Resources.Load(<0x00024>:36)
at <GetAssetFromBundleHelper>c__Iterator4`1.MoveNext(<0x001ab>:427)
at <Module>.runtime_invoke_bool__this__(Native Method)
at Unknown.6abd386b(Unknown Source)

 

I just released a game yesterday and I have seen the same issue on at least 1 out of ~300 installs on the first day. I received two error reports through Play regarding the issue from what seems like the same user, because both list the odd device "smdk4412" which only seems to relate to Linux version 3 from what I can find in google: https://github.com/ptmr3/smdk4412

I'm not sure if this is a mem leak or Unity compatibility type of issue since its pointing to the base kernal...or if the person who submitted the error was playing with a strange device or OS of some kind and I should just ignore the special case. I will contact support just in case it is report able.

Report:

java.lang.Error: FATAL EXCEPTION [GLThread 338]
Unity version : 4.2.2f1
Device model : S.LSI Division, Samsung Electronics Co., Ltd. WORKTAB Q10
Device fingerprint: Android/full_smdk4412/smdk4412:4.2.2/JDQ39/eng.utsw1.20130805.182047:eng/test-keys

Caused by: java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
Build fingerprint: 'Android/full_smdk4412/smdk4412:4.2.2/JDQ39/eng.utsw1.20130805.182047:eng/test-keys'
Revision: '0'
pid: 16993, tid: 17013, name: UnityMain >>> com.dmtsource.emergencylandingdisaster <<<
r0 7358a448 r1 00000000 r2 00000001 r3 00000000
r4 7358a448 r5 00000030 r6 73633080 r7 0000000c
r8 00000010 r9 00000001 sl 00000c80 fp 679fb3a0
ip 679ea248 sp 697f12d0 lr 400d63c3 pc 691f7464 cpsr 0000000b

at libMali.00026464(Native Method)
at libMali.00027fac(Native Method)
at libMali.000270fc(Native Method)
at libMali.000400f0(Native Method)
at libMali.shim_glDrawElements(shim_glDrawElements:76)
at libunity.003af708(Native Method)
at libunity.003b1634(Native Method)
at libunity.002136c8(Native Method)
at libunity.001b1dc8(Native Method)
at libunity.002138a0(Native Method)
at libunity.001347ac(Native Method)
at libunity.00136e28(Native Method)
at libunity.0013b638(Native Method)
at libunity.00144864(Native Method)
at libunity.00164d24(Native Method)
at libunity.00168d24(Native Method)
at libunity.002c941c(Native Method)
at libunity.002c9dd0(Native Method)
at libunity.003f6304(Native Method)
at libunity.003f63a8(Native Method)
at libdvm.dvmPlatformInvoke(dvmPlatformInvoke:112)
at libdvm.dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)(dvmCallJNIMethod:396)
at libdvm.000276a0(Native Method)
at libdvm.dvmInterpret(Thread*, Method const*, JValue*)(dvmInterpret:184)
at libdvm.dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)(dvmCallMethodV:272)
at libdvm.dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)(dvmCallMethod:20)
at libdvm.000547d7(Native Method)
at libc.__thread_entry(__thread_entry:72)
at libc.pthread_create(pthread_create:160)

 

I'm having someone report this similar crash to me, though it is java.lang.Error: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR)

They can't seem to launch the app anymore (this crash came as a result of updating the app). I've no idea what could be causing this or what action to tell them to take.

java.lang.Error: FATAL EXCEPTION [GLThread 242]
Unity version : 4.2.2f1
Device model : samsung ZT ICS
Device fingerprint: samsung/GT-I9100/GT-I9100:4.0.3/IML74K/20120303:eng/test-keys

Caused by: java.lang.Error: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 00008892
Build fingerprint: 'samsung/GT-I9100/GT-I9100:4.0.3/IML74K/20120303:eng/test-keys'
Revision: '32'
pid: 7644, tid: 7673, name: UnityMain >>> com.beliefengine.handyapp <<<
r0 00605680 r1 5ed5e068 r2 5ed746b0 r3 5ecdc078
r4 00008892 r5 0000000f r6 0000000e r7 00605a40
r8 0000000c r9 5ecdc040 sl 5ed5e268 fp 00008892
ip 5b84d140 sp 5b84d104 lr 5a33cd6c pc 5a5f835c cpsr 0000000b

at libunity.0045935c(Native Method)

 

any news on this ? I got the same error 4 years later

 

I am also getting the same error

java.lang.Error: FATAL EXCEPTION [UnityMain]
Unity version : 4.6.4f1
Device model : samsung GT-I9505
Device fingerprint: samsung/jfltexx/jflte:5.0.1/LRX22C/I9505XXUHOJ3:user/release-keys

Caused by: java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 999479b0
Build fingerprint: 'samsung/jfltexx/jflte:5.0.1/LRX22C/I9505XXUHOJ3:user/release-keys'
Revision: '11'
pid: 4637, tid: 4656, name: main >>> com.EIZSoft.Swiper <<<
r0 999479b0 r1 99948000 r2 fffffe5c r3 99948000
r4 999479b0 r5 00000001 r6 99947ffc r7 b43b3000
r8 979b6de0 r9 b4d11c00 sl 00000000 fp b38038ac
ip a1415ed0 sp b3803880 lr a13310b4 pc a1331024 cpsr 35303539

at libmono.002c9024(Native Method)
at libmono.GC_push_all_stack(GC_push_all_stack:72)
at libmono.002d46b0(Native Method)
at libmono.002d4780(Native Method)
at libmono.002ce808(Native Method)
at libmono.002cae24(Native Method)
at libmono.002c73fc(Native Method)
at libmono.002bd38c(Native Method)
at libmono.002bcdd0(Native Method)
at libmono.002bdc34(Native Method)
at libmono.002bdcd4(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.00208a3c(Native Method)
at libunity.0029f228(Native Method)
at libunity.003d27c8(Native Method)
at libunity.003dda4c(Native Method)
at data@app@com.00435593(Native Method)

 

we are also getting similar issue, we are using Unity 5.3.5p7 pro version, looks like they haven't fixed this issue in any versions.

 

We are also getting this issue in Unity 5.4.3f1, has anyone reported an issue on this?

edit: looks like it, but it's closed as "not reproducable" :/
https://issuetracker.unity3d.com/issues/android-crash-fatal-signal-11-sigsegv-on-some-devices

 

one user has an instant crash after the app start:

java.lang.Error: FATAL EXCEPTION [main]
Unity version : 5.4.3f1
Device model : samsung SM-G930T
Device fingerprint: samsung/heroqltetmo/heroqltetmo:6.0.1/MMB29M/G930TUVU4APK1:user/release-keys

Caused by: java.lang.Error: signal 6 (SIGABRT), code -6 (?), fault addr --------
Build fingerprint: 'samsung/heroqltetmo/heroqltetmo:6.0.1/MMB29M/G930TUVU4APK1:user/release-keys'
Revision: '14'
pid: 11958, tid: 12131, name: Thread-5992 >>> com.test.abc <<<
r0 00000000 r1 00002f63 r2 00000006 r3 d4459978
r4 d4459980 r5 d4459930 r6 00000000 r7 0000010c
r8 00000043 r9 f427de44 sl d3b5a5bb fp f4263d10
ip 00000006 sp d4458d18 lr f6f3b12d pc f6f3d528 cpsr 4d4d2f31

at libc.tgkill(tgkill:12)
at libc.pthread_kill(pthread_kill:32)
at libc.raise(raise:10)
at libc.__libc_android_abort(__libc_android_abort:34)
at libc.abort(abort:4)
at libc.abort(abort:4)
at libc.abort(abort:4)
at libc.abort(abort:4) ​

...

 

Same here just with the Store download I couldn´t reproduce it building directly to our devices.

 

We have 5% of our users crashing due to this.

Fatal Exception: java.lang.Error: FATAL EXCEPTION [UnityMain]
Unity version : 5.4.3f1
Device model : Lenovo Lenovo A5500-HV
Device fingerprint: Lenovo/A5500-HV/A5500-HV:4.4.2/KOT49H/A5500HV_A442_000_017_140709_ROW:user/release-keys


Caused by java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
Build fingerprint: 'Lenovo/A5500-HV/A5500-HV:4.4.2/KOT49H/A5500HV_A442_000_017_140709_ROW:user/release-keys'
Revision: '0'
pid: 10288, tid: 10341, name: UnityMain >>> com.ilmfinity.tapcreo <<<
r0 62e15f08 r1 00000008 r2 00000000 r3 00000000
r4 61e018e6 r5 62e14c70 r6 62f6fd80 r7 fffff0d4
r8 00001298 r9 00000028 sl 00000001 fp 00000002
ip 00000028 sp 636a5978 lr ffffffff pc 6145d718 cpsr 35412f48

at libunity.004d5718(Unknown Source)
at libunity.003350fc(Unknown Source)
at libunity.0030f368(Unknown Source)
at libunity.00360130(Unknown Source)
at libunity.0050ccbc(Unknown Source)
at libunity.0050fab0(Unknown Source)
at libdvm.dvmPlatformInvoke(dvmPlatformInvoke:112)
at libdvm.dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)(dvmCallJNIMethod:484)
at libdvm.00027ce8(Unknown Source)
at libdvm.dvmMterpStd(Thread*)(dvmMterpStd:76)
at libdvm.dvmInterpret(Thread*, Method const*, JValue*)(dvmInterpret:188)
at libdvm.dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)(dvmCallMethodV:340)
at libdvm.dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)(dvmCallMethod:20)
at libdvm.000575c5(Unknown Source)
at libc.__thread_entry(__thread_entry:72)

 

I was doing some test with this amazing plugin https://www.assetstore.unity3d.com/en/#!/content/12047 On beta builds, I could only execute the plugin one time I don´t know why, but the time I could,the debug console printed some error with the Purchasing plugin json. It´s curious because I initialize the purchasing scripts after many things like custom animated splash, some server comprovations... Not at the start of my App.

Also I tried the Android Studio Device Monitoring and this throw me errors like these :

01-20 09:18:47.718: W/ActivityManager(605): Activity pause timeout for ActivityRecord{4248bb38 u0 com.cuicuistudios.BoogiesAcademy/com.unity3d.player.UnityPlayerActivity t142}
01-20 09:18:50.441: W/InputDispatcher(605): channel '42810050 com.cuicuistudios.BoogiesAcademy/com.unity3d.player.UnityPlayerActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9

01-20 09:26:51.620: W/Unity(32757): UnityEngine.StackTraceUtility:ExtractStackTrace()
01-20 09:26:51.620: W/Unity(32757): UnityEngine.Purchasing.MiniJson:.cctor()

This last lines of errors appears in red on the devices that not work but in orange in the only device that work. Te lines that not appear on working devices are the first I put related to the UnityPlayerActivity and this other related to de "/data/app-lib" folder: (It throw many I will put just one per type of exception)

01-20 09:32:22.420: E/CRASH(562): #00 pc 006a8af4 /data/app-lib/com.cuicuistudios.BoogiesAcademy-1/libunity.so
01-20 09:32:22.421: E/CRASH(562): 62471a74 5ff51b3c /data/app-lib/com.cuicuistudios.BoogiesAcademy-1/libunity.so

Hope some Unity Support can help us. I also sent a mail to Google.

Good luck!!!!

 

Hi guys!

I have new information, directly from the Google Developer support. I sent them this forum post and some of our java errors and logs. And this morning they came with the best issue solution I ever seeing.... Let me copy it.

"
Hi There,


Thanks for contacting Google Play Developer Support.

We looked into this behavior that you're seeing and confirmed that this is a problem with particular devices and not with Google Play(or your app). However, we recommend to have your users try the following:

• Clear cache data on their devices
• Have the users delete their Google Play accounts and re-add the account and see if the issues resolves.

If those troubleshooting steps didn't resolve the issue, you can direct the users contacting Google Play User Support:

https://support.google.com/googleplay/?hl=en#topic=3364260&contact=1

If you have any issues distributing Android apps through the Google Play Developer Console, please let me know.

Regards,
Vivian
Google Play Developer Support
"
Funny right? Of course we tried it on our devices and the issue still there...

Did some one have better luck?

 

Similar thign here. 40 crashes... Nobody from Unity can chime in on this?

Code (csharp):

1.  
2. java.lang.Error: FATAL EXCEPTION [UnityMain]
3. Unity version : 5.4.3p4
4. Device model : samsung SM-G386T1
5. Device fingerprint: samsung/afyonlteMetroPCS/afyonlteMetroPCS:4.4.2/KOT49H/G386T1UVU1AOH2:user/release-keys
6.  
7. Caused by: java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000008
8. Build fingerprint: 'samsung/afyonlteMetroPCS/afyonlteMetroPCS:4.4.2/KOT49H/G386T1UVU1AOH2:user/release-keys'
9. Revision: '6'
10. pid: 32244, tid: 32262, name: main >>> com.tinytitanstudios.TrainChu <<<
11. r0 79c49150 r1 000000f8 r2 00000008 r3 ffffffff
12. r4 789277ec r5 00000000 r6 00100000 r7 00000000
13. r8 00800000 r9 7892790c sl 789277ec fp 000532aa
14. ip 78551248 sp 78927788 lr 77803478 pc 779d2370 cpsr 43506f72
15.  
16. at libunity.003de370(Native Method)
17. at libunity.003de0f4(Native Method)
18. at libunity.003ddc84(Native Method)
19. at libunity.003b7808(Native Method)
20. at libunity.00415610(Native Method)
21. at libunity.0041298c(Native Method)
22. at libunity.00412dc4(Native Method)
23. at libunity.001e4bb8(Native Method)
24. at libunity.003df558(Native Method)
25. at libunity.003df7b8(Native Method)
26. at libunity.0050e620(Native Method)
27. at libunity.00511400(Native Method)
28. at libdvm.dvmPlatformInvoke(dvmPlatformInvoke:112)
29. at libdvm.dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)(dvmCallJNIMethod:398)
30. at libdvm.0002a320(Native Method)
31. at libdvm.dvmMterpStd(Thread*)(dvmMterpStd:76)
32. at libdvm.dvmInterpret(Thread*, Method const*, JValue*)(dvmInterpret:184)
33. at libdvm.dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)(dvmCallMethodV:336)
34. at libdvm.dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)(dvmCallMethod:20)
35. at libdvm.00058c8b(Native Method)
36. at libc.__thread_entry(__thread_entry:72)
37. at libc.pthread_create(pthread_create:240)
38.  

Another one:

Code (csharp):

1.  
2. java.lang.Error: FATAL EXCEPTION [UnityMain]
3. Unity version : 5.4.3p4
4. Device model : samsung SM-N915V
5. Device fingerprint: Verizon/tbltevzw/tbltevzw:5.0.1/LRX22C/N915VVRS2BPC1:user/release-keys
6.  
7. Caused by: java.lang.Error: signal 6 (SIGABRT), code -6 (?), fault addr --------
8. Build fingerprint: 'Verizon/tbltevzw/tbltevzw:5.0.1/LRX22C/N915VVRS2BPC1:user/release-keys'
9. Revision: '15'
10. pid: 23183, tid: 23251, name: main >>> com.tinytitanstudios.TrainChu <<<
11. r0 00000000 r1 00005ad3 r2 00000006 r3 00000000
12. r4 b3b01db8 r5 00000006 r6 00000002 r7 0000010c
13. r8 00000000 r9 8e39abc1 sl b3b00c4c fp 5d9f1dd0
14. ip 00005ad3 sp b3b00a10 lr b6e97fc9 pc b6ebb600 cpsr 4e2f4332
15.  
16. at libc.tgkill(tgkill:12)
17. at libc.pthread_kill(pthread_kill:52)
18. at libc.raise(raise:10)
19. at libc.__libc_android_abort(__libc_android_abort:36)
20. at libc.abort(abort:4)
21. at libc.abort(abort:4)
22. at libc.abort(abort:4)
23. at libc.abort(abort:4)
24. at libc.abort(abort:4)
25. at libc.abort(abort:4)
26. at libc.abort(abort:4)
27. at libc.abort(abort:4)
28. at libc.abort(abort:4)
29. at libc.abort(abort:4)
30. at libc.abort(abort:4)
31. at libc.abort(abort:4)
32. at libc.abort(abort:4)
33. at libc.abort(abort:4)
34. at libc.abort(abort:4)
35. at libc.abort(abort:4)
36. at libc.abort(abort:4)
37. at libc.abort(abort:4)
38. at libc.abort(abort:4)
39. at libc.abort(abort:4)
40. at libc.abort(abort:4)
41. at libc.abort(abort:4)
42. at libc.abort(abort:4)
43. at libc.abort(abort:4)
44. at libc.abort(abort:4)
45. at libc.abort(abort:4)
46. at libc.abort(abort:4)
47. at libc.abort(abort:4)
48.  

 

Hi!

I replied again to Google Play and they said me the same thing. Nothing is wrong with the store or the app. And insist me to call the user support, so I called them few minutes ago, and as you may think they could not help us...

I´m going to contact again with developer support and try to open a new Unity issue tracker on . The previous were closed because Unity can´t reproduce the error. But maybe if we reopen it...

Did some one have any luck?

 

@CuiCuiStudios Is this something you've always had or just recently? In my case, we released a bad update had some memory issues, so devices were running out of memory etc. A lot of these crashes came after that release. It could just be that those error messages aren't really teling what the issue is, but is just a side effect of it.

 

Same here:
02-05 23:25:22.560 19553-19553/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-05 23:25:22.561 19553-19553/? A/DEBUG: Build fingerprint: 'google/marlin/marlin:7.1.1/NMF26U/3562008:user/release-keys'
02-05 23:25:22.561 19553-19553/? A/DEBUG: Revision: '0'
02-05 23:25:22.561 19553-19553/? A/DEBUG: ABI: 'arm'
02-05 23:25:22.561 19553-19553/? A/DEBUG: pid: 19413, tid: 19430, name: UnityMain >>> <<<
02-05 23:25:22.561 19553-19553/? A/DEBUG: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x12f08000
02-05 23:25:22.561 19553-19553/? A/DEBUG: r0 0028f51e r1 00000000 r2 12f08000 r3 12f08000
02-05 23:25:22.562 19553-19553/? A/DEBUG: r4 0000ffff r5 12c8db80 r6 00200956 r7 e612f668
02-05 23:25:22.562 19553-19553/? A/DEBUG: r8 00000043 r9 e617eef0 sl e6130269 fp e613029a
02-05 23:25:22.562 19553-19553/? A/DEBUG: ip 00000000 sp e4d67740 lr 3861faa0 pc e605d5d2 cpsr 800d0030
02-05 23:25:22.580 19553-19553/? A/DEBUG: backtrace:
02-05 23:25:22.580 19553-19553/? A/DEBUG: #00 pc 0034c5d2 /system/lib/libart.so (_ZN3art14CountUtf8BytesEPKtj+67)
02-05 23:25:22.580 19553-19553/? A/DEBUG: #01 pc 0027d33b /system/lib/libart.so (_ZN3art3JNI17GetStringUTFCharsEP7_JNIEnvP8_jstringPh+430)
02-05 23:25:22.580 19553-19553/? A/DEBUG: #02 pc 0099ca88 /data/app2/lib/arm/libunity.so

I used android ndk addr2line for checking stack:
C:\android-ndk\toolchains\arm-linux-androideabi-4.9\prebuilt\windows-x86_64\bin\arm-linux-androideabi-addr2line.exe -Cfe "C:\Program Files\Unity\Editor\Data\PlaybackEngines\AndroidPlayer\Variations\mono\Release\Symbols\armeabi-v7a\libunity.sym.so"

0034c5d2 ->

Code (CSharp):

1. std::pair<std::_Rb_tree_iterator<std::pair<ShaderLab::FastPropertyName const, float> >, bool> std::_Rb_tree<ShaderLab::FastPropertyName, std::pair<ShaderLab::FastPropertyName const, float>, std::_Select1st<std::pair<ShaderLab::FastPropertyName const, float> >, std::less<ShaderLab::FastPropertyName>, std::allocator<std::pair<ShaderLab::FastPropertyName const, float> > >::_M_insert_unique<std::pair<ShaderLab::FastPropertyName, float> >(std::pair<ShaderLab::FastPropertyName, float>&&)
2. ??:?

So in my case it seems to be a problem with a shader. It crashes on every android device since update to Unity 5.5... I found some advice to not use standard shader on android because of incompatibility - but I was not sucessful!

 

@vexe No, this started on January after a Google Play Update. In some of our test devices we updated the app as a normal user would do and the app runs perfect, however the issue does appear after uninstalling and then reinstalling it again, it only happens if we install from the store, not on a direct build.

Yesterday I was doing some tests, I updated the Android project to the last Unity 5.5 patch, after a new build with this Unity version the app runs in the devices where it previously did not but it gets stuck on some part of the code , and using the Unity Log Viewer plugin I found out that on these devices the App can't use the Instantiate Method.
Tried removing the Instantiate Method and the applications works until some new error (I am dealing with that now).

Even with the app starting and taking some steps through it, a java error appears in the debug console anyway...

"java.io.FileNotFoundException: assets/build_info.txt"

With our metrics we saw that there are no similarities about OS or hardware between devices that work and devices that do not; I am sure that it has something to do with the Google Update (at least in our case).

Unity and Google need to find the real problem of these issues.

 

I am in a situation that may help you

Code (CSharp):

1.  
2. 109-05 07:39:58.178 14830 14901 E Unity :
3. 209-05 07:39:58.178 14830 14901 E Unity : (Filename: Line: 483)
4. 309-05 07:39:58.178 14830 14901 E Unity :
5. 409-05 07:39:58.197 14830 14900 E Unity : Unable to open archive file: /storage/emulated/0/Android/data/com.company.project/files/c31b32364ce19ca8fcd150a417ecce58/b739559997f98a21550e49f8846ad606.u3d
6. 509-05 07:39:58.197 14830 14900 E Unity :
7. 609-05 07:39:58.197 14830 14900 E Unity : (Filename: Line: 483)
8. 709-05 07:39:58.197 14830 14900 E Unity :
9. 809-05 07:39:58.212 14830 14903 E Unity : Unable to open archive file: /storage/emulated/0/Android/obb/com.company.project/main.10006.com.company.project.obb!assets/c31b32364ce19ca8fcd150a417ecce58/b739559997f98a21550e49f8846ad606.u3d
10. 909-05 07:39:58.212 14830 14903 E Unity :
11. 1009-05 07:39:58.212 14830 14903 E Unity : (Filename: Line: 483)
12. 1109-05 07:39:58.212 14830 14903 E Unity :
13. 1209-05 07:39:58.228 14830 14897 E Unity : Unable to open archive file: /storage/emulated/0/Android/data/com.company.project/files/c31b32364ce19ca8fcd150a417ecce58/b739559997f98a21550e49f8846ad606.u3d
14. 1309-05 07:39:58.228 14830 14897 E Unity :
15. 1409-05 07:39:58.228 14830 14897 E Unity : (Filename: Line: 483)
16. 1509-05 07:39:58.228 14830 14897 E Unity :
17. 1609-05 07:39:58.245 14830 14904 E Unity : Unable to open archive file: /storage/emulated/0/Android/obb/com.company.project/main.10006.com.company.project.obb!assets/c31b32364ce19ca8fcd150a417ecce58/b739559997f98a21550e49f8846ad606.u3d
18. 1709-05 07:39:58.245 14830 14904 E Unity :
19. 1809-05 07:39:58.245 14830 14904 E Unity : (Filename: Line: 483)
20. 1909-05 07:39:58.245 14830 14904 E Unity :
21. 2009-05 07:39:58.264 14830 14900 E CRASH : signal 6 (SIGABRT), code -6 (?), fault addr --------
22. 2109-05 07:39:58.264 14830 14900 E CRASH : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
23. 2209-05 07:39:58.264 14830 14900 E CRASH : Build fingerprint: 'Xiaomi/santoni/santoni:6.0.1/MMB29M/V8.2.10.0.MAMMIEA:user/release-keys'
24. 2309-05 07:39:58.265 14830 14900 E CRASH : Revision: '0'
25. 2409-05 07:39:58.265 14830 14900 E CRASH : pid: 14830, tid: 14900, name: BackgroundWorke >>> com.company.project <<<
26. 2509-05 07:39:58.265 14830 14900 E CRASH : r0 00000000 r1 00003a34 r2 00000006 r3 d8baf978
27. 2609-05 07:39:58.265 14830 14900 E CRASH : r4 d8baf980 r5 d8baf930 r6 00000002 r7 0000010c
28. 2709-05 07:39:58.265 14830 14900 E CRASH : r8 00000000 r9 00000100 sl dc606b68 fp d8baef28
29. 2809-05 07:39:58.265 14830 14900 E CRASH : ip 00000006 sp d8baeea8 lr f72e7f5d pc f72ea358 cpsr 322e3856
30. 2909-05 07:39:58.265 14830 14900 E CRASH :
31. 3009-05 07:39:58.265 14830 14900 E CRASH : backtrace:
32. 3109-05 07:39:58.484 14830 14900 E CRASH : #00 pc 00044358 /system/lib/libc.so (tgkill+12)
33. 3209-05 07:39:58.485 14830 14900 E CRASH : #01 pc 00041f59 /system/lib/libc.so (pthread_kill+32)
34. 3309-05 07:39:58.485 14830 14900 E CRASH : #02 pc 0001ba6f /system/lib/libc.so (raise+10)
35. 3409-05 07:39:58.485 14830 14900 E CRASH : #03 pc 00018c11 /system/lib/libc.so (__libc_android_abort+34)
36. 3509-05 07:39:58.485 14830 14900 E CRASH : #04 pc 000167d0 /system/lib/libc.so (abort+4)
37. 3609-05 07:39:58.485 14830 14900 E CRASH : #05 pc 000167d0 /system/lib/libc.so (abort+4)
38.  
39. 5709-05 07:39:58.485 14830 14900 E CRASH : #26 pc 000167d0 /system/lib/libc.so (abort+4)
40. 5809-05 07:39:58.485 14830 14900 E CRASH : #27 pc 000167d0 /system/lib/libc.so (abort+4)
41. 5909-05 07:39:58.485 14830 14900 E CRASH : #28 pc 000167d0 /system/lib/libc.so (abort+4)
42. 6009-05 07:39:58.485 14830 14900 E CRASH : #29 pc 000167d0 /system/lib/libc.so (abort+4)
43. 6109-05 07:39:58.485 14830 14900 E CRASH : #30 pc 000167d0 /system/lib/libc.so (abort+4)
44. 6209-05 07:39:58.485 14830 14900 E CRASH : #31 pc 000167d0 /system/lib/libc.so (abort+4)
45. 6309-05 07:39:58.485 14830 14900 E CRASH :
46. 6409-05 07:39:58.485 14830 14900 E CRASH : stack:
47. 6509-05 07:39:58.486 14830 14900 E CRASH : d8baee68 00000000
48. 6609-05 07:39:58.486 14830 14900 E CRASH : d8baee6c 00000000
49. 6709-05 07:39:58.486 14830 14900 E CRASH : d8baee70 00000000
50. 6809-05 07:39:58.486 14830 14900 E CRASH : d8baee74 00000000
51. 6909-05 07:39:58.486 14830 14900 E CRASH : d8baee78 00000000
52. 7009-05 07:39:58.486 14830 14900 E CRASH : d8baee7c 00000000
53. 7109-05 07:39:58.486 14830 14900 E CRASH : d8baee80 ffffffdf
54. 7209-05 07:39:58.486 14830 14900 E CRASH : d8baee84 00000000
55. 7309-05 07:39:58.486 14830 14900 E CRASH : d8baee88 d8baf930 [stack:14900]
56. 7409-05 07:39:58.486 14830 14900 E CRASH : d8baee8c d8baf930 [stack:14900]
57. 7509-05 07:39:58.486 14830 14900 E CRASH : d8baee90 00000002
58. 7609-05 07:39:58.486 14830 14900 E CRASH : d8baee94 f72e7cd9 /system/lib/libc.so (__pthread_internal_find(long)+36)
59. 7709-05 07:39:58.486 14830 14900 E CRASH : d8baee98 d8baf978 [stack:14900]
60. 7809-05 07:39:58.487 14830 14900 E CRASH : d8baee9c d8baf980 [stack:14900]
61. 7909-05 07:39:58.487 14830 14900 E CRASH : d8baeea0 d8baf930 [stack:14900]
62. 8009-05 07:39:58.487 14830 14900 E CRASH : d8baeea4 f72e7f4d /system/lib/libc.so (pthread_kill+20)
63. 8109-05 07:39:58.487 14830 14900 E CRASH : #00 d8baeea8 d8baf978 [stack:14900]
64. 8209-05 07:39:58.487 14830 14900 E CRASH : ........ ........
65. 8309-05 07:39:58.487 14830 14900 E CRASH : #01 d8baeea8 d8baf978 [stack:14900]
66. 8409-05 07:39:58.487 14830 14900 E CRASH : d8baeeac 00000006
67. 8509-05 07:39:58.487 14830 14900 E CRASH : d8baeeb0 00000000
68. 8609-05 07:39:58.487 14830 14900 E CRASH : d8baeeb4 dd3dad2c [stack:14876]
69. 8709-05 07:39:58.487 14830 14900 E CRASH : d8baeeb8 dd3db930 [stack:14876]
70. 8809-05 07:39:58.487 14830 14900 E CRASH : d8baeebc f72c1a73 /system/lib/libc.so (raise+14)
71. 8909-05 07:39:58.487 14830 14900 E CRASH : #02 d8baeec0 d8baeecc [stack:14900]
72. 9009-05 07:39:58.487 14830 14900 E CRASH : d8baeec4 f72bec15 /system/lib/libc.so (__libc_android_abort+38)
73. 9109-05 07:39:58.487 14830 14900 E CRASH : #03 d8baeec8 00000000
74. 9209-05 07:39:58.487 14830 14900 E CRASH : d8baeecc ffffffdf
75. 9309-05 07:39:58.488 14830 14900 E CRASH : d8baeed0 dc22129a /data/app/com.tapenjoy.warx-1/lib/arm/libil2cpp.so
76. 9409-05 07:39:58.488 14830 14900 E CRASH : d8baeed4 00000000
77. 9509-05 07:39:58.488 14830 14900 E CRASH : d8baeed8 00000001
78. 9609-05 07:39:58.488 14830 14900 E CRASH : d8baeedc dc0900a0 /data/app/com.tapenjoy.warx-1/lib/arm/libil2cpp.so
79. 9709-05 07:39:58.488 14830 14900 E CRASH : d8baeee0 00002150
80. 9809-05 07:39:58.488 14830 14900 E CRASH : d8baeee4 00002150
81. 9909-05 07:39:58.488 14830 14900 E CRASH : d8baeee8 00000004
82. 10009-05 07:39:58.488 14830 14900 E CRASH : d8baeeec f72bc7d4 /system/lib/libc.so (__bionic_clone)
83. 10109-05 07:39:58.488 14830 14900 E CRASH : #04 d8baeef0 abbef4e9 [heap]
84. 10209-05 07:39:58.488 14830 14900 E CRASH : ........ ........
85. 10309-05 07:39:58.488 14830 14900 E CRASH : #05 d8baeef0 abbef4e9 [heap]
86. 10409-05 07:39:58.488 14830 14900 E CRASH : ........ ........
87. 10509-05 07:39:58.488 14830 14900 E CRASH : #06 d8baeef0 abbef4e9 [heap]
88. 10609-05 07:39:58.488 14830 14900 E CRASH : ........ ........
89. 10709-05 07:39:58.488 14830 14900 E CRASH : #07 d8baeef0 abbef4e9 [heap]
90. 10809-05 07:39:58.488 14830 14900 E CRASH : ........ ........
91. 10909-05 07:39:58.488 14830 14900 E CRASH : #08 d8baeef0 abbef4e9 [heap]
92. 11009-05 07:39:58.488 14830 14900 E CRASH : ........ ........
93. 11109-05 07:39:58.489 14830 14900 E CRASH : #09 d8baeef0 abbef4e9 [heap]
94. 11209-05 07:39:58.489 14830 14900 E CRASH : ........ ........
95. 11309-05 07:39:58.489 14830 14900 E CRASH : #10 d8baeef0 abbef4e9 [heap]
96. 11409-05 07:39:58.489 14830 14900 E CRASH : ........ ........
97. 11509-05 07:39:58.489 14830 14900 E CRASH : #11 d8baeef0 abbef4e9 [heap]
98. 11609-05 07:39:58.489 14830 14900 E CRASH : ........ ........
99. 11709-05 07:39:58.489 14830 14900 E CRASH : #12 d8baeef0 abbef4e9 [heap]
100. 11809-05 07:39:58.489 14830 14900 E CRASH : ........ ........
101. 11909-05 07:39:58.489 14830 14900 E CRASH : #13 d8baeef0 abbef4e9 [heap]
102. 12009-05 07:39:58.489 14830 14900 E CRASH : ........ ........
103. 12109-05 07:39:58.489 14830 14900 E CRASH : #14 d8baeef0 abbef4e9 [heap]
104. 12209-05 07:39:58.489 14830 14900 E CRASH : ........ ........
105. 12309-05 07:39:58.489 14830 14900 E CRASH : #15 d8baeef0 abbef4e9 [heap]
106. 12409-05 07:39:58.489 14830 14900 E CRASH : ........ ........
107. 12509-05 07:39:58.489 14830 14900 E CRASH : #16 d8baeef0 abbef4e9 [heap]
108. 12609-05 07:39:58.489 14830 14900 E CRASH : ........ ........
109. 12709-05 07:39:58.489 14830 14900 E CRASH : #17 d8baeef0 abbef4e9 [heap]
110. 12809-05 07:39:58.489 14830 14900 E CRASH : ........ ........
111. 12909-05 07:39:58.489 14830 14900 E CRASH : #18 d8baeef0 abbef4e9 [heap]
112. 13009-05 07:39:58.489 14830 14900 E CRASH : ........ ........
113. 13109-05 07:39:58.490 14830 14900 E CRASH : #19 d8baeef0 abbef4e9 [heap]
114. 13209-05 07:39:58.490 14830 14900 E CRASH : ........ ........
115. 13309-05 07:39:58.490 14830 14900 E CRASH : #20 d8baeef0 abbef4e9 [heap]
116. 13409-05 07:39:58.490 14830 14900 E CRASH : ........ ........
117. 13509-05 07:39:58.490 14830 14900 E CRASH : #21 d8baeef0 abbef4e9 [heap]
118. 13609-05 07:39:58.490 14830 14900 E CRASH : ........ ........
119. 13709-05 07:39:58.490 14830 14900 E CRASH : #22 d8baeef0 abbef4e9 [heap]
120. 13809-05 07:39:58.490 14830 14900 E CRASH : ........ ........
121. 13909-05 07:39:58.490 14830 14900 E CRASH : #23 d8baeef0 abbef4e9 [heap]
122. 14009-05 07:39:58.490 14830 14900 E CRASH : ........ ........
123. 14109-05 07:39:58.490 14830 14900 E CRASH : #24 d8baeef0 abbef4e9 [heap]
124. 14209-05 07:39:58.490 14830 14900 E CRASH : ........ ........
125. 14309-05 07:39:58.490 14830 14900 E CRASH : #25 d8baeef0 abbef4e9 [heap]
126. 14409-05 07:39:58.490 14830 14900 E CRASH : ........ ........
127. 14509-05 07:39:58.490 14830 14900 E CRASH : #26 d8baeef0 abbef4e9 [heap]
128. 14609-05 07:39:58.490 14830 14900 E CRASH : ........ ........
129. 14709-05 07:39:58.490 14830 14900 E CRASH : #27 d8baeef0 abbef4e9 [heap]
130. 14809-05 07:39:58.490 14830 14900 E CRASH : ........ ........
131. 14909-05 07:39:58.490 14830 14900 E CRASH : #28 d8baeef0 abbef4e9 [heap]
132. 15009-05 07:39:58.490 14830 14900 E CRASH : ........ ........
133. 15109-05 07:39:58.490 14830 14900 E CRASH : #29 d8baeef0 abbef4e9 [heap]
134. 15209-05 07:39:58.490 14830 14900 E CRASH : ........ ........
135. 15309-05 07:39:58.490 14830 14900 E CRASH : #30 d8baeef0 abbef4e9 [heap]
136. 15409-05 07:39:58.490 14830 14900 E CRASH : ........ ........
137. 15509-05 07:39:58.491 14830 14900 E CRASH : #31 d8baeef0 abbef4e9 [heap]
138.  

the point is below

Code (CSharp):

1.  Unable to open archive file: /storage/emulated/0/Android/data/com.company.project/files/c31b32364ce19ca8fcd150a417ecce58/b739559997f98a21550e49f8846ad606.u3d

I have always loaded a non-existent assetbundle to cause this error.

 

Это все из-за загрузки больших текстур / атласов. Если вы уменьшите их, эта ошибка пройдет. Так же может вызывать эту ошибку большие аудиофайлы .

 

(begin: translation)

This is all due to the loading of large textures / atlases. If you reduce them, this error will pass. It can also cause this error large audio files.

(end: translation)

 

Все аудиофайлы изначально сжаты максимум до 1-2 мб. Максимальный атлас 1024 пикселя. Других больших ресурсов нет. Словил эту ошибку на своем устройстве. Игра вылетает сразу при запуске перед появлением заставки юнити. При чем если я заливаю апк прямо на телефон - все работает. Если я заливаю этот апк в консоль и скачиваю с маркета - вылетает. Пробовал перезагружать ПК, билдить заново и заливать новую версию в маркет - тоже вытелает. Консоль показывает что я пока единственный с такой ошибкой. Есть второй точно такой телефон как у меня с такой-же версией прошивки - на нем все работает. Как такое может быть? Причем раньше и у меня работало а потом в один момент начало вылетать. Пробовал удалять игру, чистить после нее клинерами, перезапускать телефон. Ставлю с маркета и опять вылет.

Code (JavaScript):

1. java.lang.Error: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0000007a112e4fe0
2. Build fingerprint: 'HUAWEI/INE-LX1/HWINE:9/HUAWEIINE-L21/215C432:user/release-keys'
3. Revision: '0'
4. pid: 22502, tid: 22528, name: UnityMain  >>> com.zoox.iceboat <<<
5. x0   0000007a0e23fb60  x1   0000007a0c4873a0  x2   0000007a0c4873a0  x3   0000000000000000
6. x4   0000007a0c487500  x5   0000000000000004  x6   0000007ab51e1000  x7   000000000037feb0
7. x8   0000007a0e5f07b0  x9   6db6db6db6db6db7  x10  0000007a112e502c  x11  0000000000020116
8. x12  00000000000005b9  x13  0000000000001e00  x14  0000000000000180  x15  aaaaaaaaaaaaaaab
9. x16  0000007aaf7b3250  x17  0000007aaf6e22b0  x18  0000000000000000  x19  0000007a112e5078
10. x20  0000007a0e5eeb78  x21  0000007a112e502d  x22  0000000000000081  x23  0000000000000038
11. x24  0000000000000102  x25  0000007a0cbd9106  x26  0000007a0e191cb4  x27  0000007a0cbd90b8
12. x28  0000007a0e672000  x29  0000007a112e5010  x30  0000007a0da68fe0
13. sp   0000007a112e5010  pc   0000007a0da68e50  pstate 0000000020000000
14. at [vdso].(
15.   at split_config. (0)
16.   at split_config. (0)
17.   at split_config. (0)
18.   at split_config. (0)
19.   at split_config. (0)
20.   at split_config. (0)
21.   at split_config. (0)
22.   at split_config. (0)
23.   at split_config. (0)
24.   at split_config. (0)
25.   at split_config. (0)
26.   at split_config. (0)
27.   at split_config. (0)
28.   at split_config. (0)
29.   at split_config. (0)
30.   at split_config. (0)
31.   at split_config. (0)
32.   at split_config. (0)
33.   at split_config. (0)
34.   at split_config. (0)
35.   at split_config. (0)
36.   at split_config. (0)
37.   at split_config. (0)
38.   at split_config. (0)
39.   at split_config. (0)
40.   at split_config. (0)
41.   at split_config. (0)
42.   at split_config. (0)
43.   at split_config. (0)
44.   at split_config. (0)
45.   at split_config. (0)

 

I had the same issue. According to this https://forum.unity.com/threads/unity-android-build-crash-when-using-arm64-with-il2cpp.674200/ I set

<application
tools:replace="android:allowBackup"
android:allowBackup="false"
...

in AndroidManifest.xml. This solved my crash on Huawei P20 pro.

 

We are having some sort of same issue:

Caused by java.lang.Error: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 000073ceb12fb090

Details attached:

 

di anyone solve this problem? i got this issue on one of our test devices. i tested all of solutions and none worked. these are the logs:

2020-10-22 01:43:39.888 740-803/? E/CRASH: pid: 740, tid: 803, name: UnityMain >>> com.darbache.pacakge<<<
2020-10-22 01:43:40.404 740-803/? E/AndroidRuntime: FATAL EXCEPTION: UnityMain
Process: com.darbache.sedarchahar, PID: 740
java.lang.Error: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Version '2019.4.8f1 (60781d942082)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'armeabi-v7a'
Build fingerprint: 'samsung/on5xeltejv/on5xelte:8.0.0/R16NW/G570FXXS3CTE5:user/release-keys'
Revision: '4'
ABI: 'arm'
Timestamp: 2020-10-22 01:43:39+0330
pid: 740, tid: 803, name: UnityMain >>> com.darbache.package<<<
uid: 10497
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xc3c2ce64
r0 c3c2ce68 r1 00000000 r2 00000354 r3 00000354
r4 b4d4ff00 r5 c3c2ce68 r6 c3c2cd50 r7 b56c2038
r8 00000022 r9 00000088 r10 b56c0628 r11 c3c2d1d0
ip e766a5e4 sp c3c2ce68 lr c1a0f924 pc e75f3004

backtrace:
#00 pc 00019004 /system/lib/libc.so (memset) (BuildId: 45bf2c44bffbcdb8a6d9888d192d01bf)
#01 pc 00403920 /data/app/com.darbache.sedarchahar-137BdDjKBXCKFeQ8fkSDJw==/lib/arm/libil2cpp.so (BuildId: 3ac131c9cee98aa099e71df876fe8964a79d776b)

at libc.memset(memset:0)
at libil2cpp.0x403920(Native Method)

 

[Edit: Solved]: This solution worked for me. I asked the user to clear the app data and try again and it worked! This has something to do with the shared preferences since that's how unity reads data from android and as mentioned by @levgen0101, you can specify backup as false to prevent this from happening in the future so that the old settings and data is not retained. Hope this helps. Cheers!


Things were working fine until I rebuilt and imported unity back into my project. I get the same (sigsev) error with code 1

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 000000000000012e Build fingerprint: 'HUAWEI/LYA-L29/HWLYA:10/HUAWEILYA-L29/10.1.0.298C636:user/release-keys' Revision: '0' pid: 28810, tid: 29412, name: UnityMain >>> "PackageName" <<< x0 0000000000000000 x1 0000000000000040 x2 0000007821c00000 x3 0000000000000007 x4 00000000000001b3 x5 000000783b342fb8 x6 00610063006f004c x7 007400610044006c x8 00000077d43e48a0 x9 ccde556eae57a803 x10 00000000000001b3 x11 0000000000000000 x12 0068002000650067 x13 0062002000730061 x14 0000000000000001 x15 00000077d42c8ae0 x16 00000077d43571b0 x17 000000793be452bc x18 00000077d45f80c0 x19 0000000000000000 x20 0000000000000040 x21 0000000000000000 x22 0000007821cebef0 x23 00000077d43be000 x24 00000077d409c490 x25 00000077d40f8b4f x26 00000077d40f8d14 x27 00000077d4098e87 x28 00000078159f9c30 x29 00000078159f9570 x30 00000077d3a1d0dc sp 00000078159f9560 pc 00000077d3a1d1f4 pstate 0000000060000000

 

Did this ever got solved ? facing same issue in 2021

 

Try clearing the app data like how I did. it might work

 

app data on cellphone ? done that , doesn't work

 

2022 and same issue,

 

2020 lts lots of signal 8 (SIGFPE), code -6 (SI_TKILL) at libc.tgkill(tgkill:12).