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.
The callstack points to the UI system, similar to what is described there: Keep Crashing on Androids - Unity Engine - Unity Discussions. Unity 5.3.3p1 included various UI fixes, but apparently this crash is not fixed yet. I don’t have an additional info or workarounds at this point :(.
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
Talked to the UI team, they are in the process of back-porting a fix to 5.3. I don’t have a specific release yet, but I would expect it to be one of the 5.3.4 patch-releases.
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.
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)
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
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)
No I don’t test it I just looked on the patch notes, and the issue was not linked (I open all of them 
Thanks a lot to Uniteam !