java.lang.Error in UnityMain in 5.3.3p1

Hi, we jump from 5.2 to 5.3 and our users report a consequent amount of crash compared to the last build.

Crash is :

java.lang.Error: FATAL EXCEPTION [main]
Unity version : 5.3.3p1
Device model : asus ASUS_Z00AD
Device fingerprint: asus/WW_Z00A/Z00A:5.0/LRX21V/2.20.40.168_20160202_1100_user:user/release-keys
Caused by: java.lang.Error: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 35b2982e
Build fingerprint: 'asus/WW_Z00A/Z00A:5.0/LRX21V/2.20.40.168_20160202_1100_user:user/release-keys'
Revision: '0'
pid: 17870, tid: 17890, name: UnityMain >>> com.plgnd.tropicalwars <<<
at libunity.000fa60b(Native Method)
at libunity.007f6d37(Native Method)
at libunity.007fdddb(Native Method)
at libunity.007fdae4(Native Method)
at libunity.008000c2(Native Method)
at libunity.003d82de(Native Method)
at libunity.005539bc(Native Method)
at libunity.00557e13(Native Method)
at data@app@com.009882ec(Native Method)

I have no idea where it comes from, or how to reproduce it, I tested one hour long on a device that usually crash often and no crash where reported during the whole hour.

If some Unity dev have an idea, I know this is a common issue but from what I saw, nobody still doesn't know where it's come from.

Thanks a lot !

 

Oh okay ! Thanks to clarify this and thanks for the thread that's seems similar to my case !

I totally don't know how to reproduce it, seems like it's linked to scene changes too in our case but I can't attach a repo since I don't know where is the crash. Seems like all devices doesn't have it too. We are on Unity 5.3.3p1.

Is there anyway to, you know, notice Unity Team that's the problem has grown on Unity 5.3 ? Or do I just have to wait and hope someone will resolve this one day ?

5.3 fix too much things for us, we can't go back to 5.2. Our game is going to be launched next month I feel bad about knowing that some users will crash randomly

 

Oh, I just check the issue tracker and saw this :

https://issuetracker.unity3d.com/is...le-scene-loads-fatal-signal-11-sigsegv-code-1

Might be my problem ! And it's fixed ! Hope it's the same thing and the 5.3.5 will appear before next month !

 

Very good, thanks A LOT for this information !

I just have to hope it comes before my game go into the wild

 

We have a version of our game in the market and lot of users are experiencing this crash and leaving the game . Please provide a patch on this at the earliest. We can't now roll back to the older Unity version as many new features are working and integrated in latest unity.

 

If I follow correctly the issue tracker, it should be on the next patch because some bug marked as "fixed in 5.3.4" as been fixed on 5.3.3p2, so 5.3.3p3 may include marked "fixed in 5.3.5" fixes

Total thought here, hoping it's coming before end of month too cause we are on the same train.

 

Seems not like to be part of 5.3.3p3

Next patch I hope, we absolutly need it to for launch

 

Oh No I don't test it I just looked on the patch notes, and the issue was not linked (I open all of them )

I'm going to test it thanks ! I'll post here if we still experience crash.

 

Very interested in this one as well. Please BenoutKat please let us know if 5.3.3p3 fixes the issue.

 

We'll send the apk to some of our players that experiencing this issue this afternoon, I'll keep you in touch.

This crash was very random so it can take more times to be sure it's fixed.

 

Great! Thank you!

 

hi,I have a same issue, I update the path 5.3.3p3
Don't know how to fix it,

1. 
   21

Android ver

1. 
   Android 4.41

Device

1. 
   LG Optimus G Pro (geefhd)1

java.lang.Error: FATAL EXCEPTION [UnityMain]
Unity version : 5.3.3p3
Device model : LGE LG-E988
Device fingerprint: lge/geefhd_open_hk/geefhd:4.4.2/KOT49I.E98820a/E98820a.1398934832:user/release-keys

Caused by: java.lang.Error: signal 6 (SIGABRT), code -6 (?), fault addr --------
Build fingerprint: 'lge/geefhd_open_hk/geefhd:4.4.2/KOT49I.E98820a/E98820a.1398934832:user/release-keys'
Revision: '10'
pid: 22933, tid: 22967, name: UnityMain >>> com.laserspaceship.myapp <<<
r0 00000000 r1 000059b7 r2 00000006 r3 00000000
r4 00000006 r5 0000000d r6 000059b7 r7 0000010c
r8 612c4a8c r9 611c6fb0 sl 5fc82c30 fp 612c2814
ip ffe8f1f1 sp 612c2760 lr 400fb215 pc 4010a1e4 cpsr 452e4939

at libc.tgkill(tgkill:12)
at libc.pthread_kill(pthread_kill:48)
at libc.raise(raise:10)
at libc.0001215b(Native Method)
at libc.abort(abort:4)
at libvrapi.00003c04(Native Method)
at libvrapi.vrapi_GetVersionString(vrapi_GetVersionString:16)
at libOVRPlugin.SystemActivities_CreateSystemActivityIntent(SystemActivities_CreateSystemActivityIntent:136)

 

This is fixed for us in 5.3.3 p3, it was random but was occurring within couple of screen transitions.

Thanks a lot guys, really appreciated..

 

Our player that experienced crash didn't notice any crash between yesterday afternoon and this morning.

Seems to be fixed Thanks a lot to Uniteam !

@bewong : Totally not the same crash, look at the top of your stack pile, it's linked to OVR plugin or vr api, this thread was a bug with UI api.

 

Hi,

We have a similar problem in Unity 5.4.0p4. When we open multiple scenes it sometimes just crash hard. Both on additive normal and async. Happens a lot on S3 devices.

java.lang.Error: FATAL EXCEPTION [UnityMain]
Unity version : 5.4.0p4
Device model : samsung GT-I9305
Device fingerprint: samsung/m3xx/m3:4.4.4/KTU84P/I9305XXUFNL1:user/release-keys

Caused by: java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
Build fingerprint: 'samsung/m3xx/m3:4.4.4/KTU84P/I9305XXUFNL1:user/release-keys'
Revision: '2'
pid: 21440, tid: 21505, name: UnityPreload >>> com.dirtybit.fra <<<
r0 00000000 r1 00000400 r2 000003ff r3 00000067
r4 00000000 r5 6b7d5790 r6 00000400 r7 00000000
r8 62619329 r9 00000000 sl 0000001b fp 76724e40
ip 0000006c sp 6315dbc8 lr 61c48d08 pc 61c48d1c cpsr 4c4e4655

at libunity.0043fd1c(Native Method)
at libunity.0043cc74(Native Method)
at libunity.0043b688(Native Method)
at libunity.00436a88(Native Method)
at libunity.00412890(Native Method)
at libunity.00412164(Native Method)
at libunity.004120a0(Native Method)
at libunity.0046d2bc(Native Method)
at libc.__thread_entry(__thread_entry:72)
at libc.pthread_create(pthread_create:240)