Crash occurs in kitkat (under opengl 2.0)

[tayl0r]

The Unity 4.5 release notes say this:

* Fixed crash on Android 4.4.2 when running on certain Adreno GPUs.

And I'm assuming that is referring to this issue. Can anyone confirm? It seems fixed to me but a guy on the tk2d forums is saying its not.

[ArenMook]

NGUI "fixed" it a few months ago (with a work-around), so it's unlikely that you will run into this even prior to 4.5, assuming you're using the latest NGUI version.

[Russel]

The bug is present again in Android 4.4.4  .

These devices are currently affected:
- Sony Xperia Z1
- Sony Xperia Z1 Compact
- Sony Xperia Z Ultra

http://www.androidcentral.com/sony-android-444-xperia-z1-compact

We use Unity 4.5.1p3 and NGUI 3.6.5.

[Russel]

We have a new (libc.memcpy) Bug Report in our Google Play Developer Console:

java.lang.Error: FATAL EXCEPTION [UnityMain]
Unity version : 4.5.1p3
Device model : HUAWEI HUAWEI G6-U10
Device fingerprint: Huawei/G6-U10/hwG6-U10:4.3/HuaweiG6-U10/C900B116:user/ota-rel-keys,release-keys

Caused by: java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 71d35000
Build fingerprint: 'Huawei/G6-U10/hwG6-U10:4.3/HuaweiG6-U10/C900B116:user/ota-rel-keys,release-keys'
Revision: '0'
pid: 23425, tid: 23460, name: UnityMain >>> de.bla.bla <<<
r0 71d35000 r1 65bcc050 r2 00000780 r3 c28c5a12
r4 00000780 r5 60c45c60 r6 71d35000 r7 65bcc010
r8 00000780 r9 00000001 sl 65bcc280 fp 00000001
ip 00000013 sp 60c45bd8 lr 00000280 pc 40064250 cpsr 2f303155

at libc.memcpy(memcpy:272)
at Unknown.0000077c(Unknown Source)

These devices are currently affected:
- Sony Xperia M2 with Android 4.3
- Huawei Ascend G6 with Android 4.3

[ArenMook]

You should submit that to Unity, Russel.

[gdeglin]

Also experiencing this problem. Seems like we'll have to delay the release of our game because of it.

Someone mentioned that NGUI 3.4.9 doesn't have this problem, but I would hate to have to downgrade so far back.

@Russel Did you submit this to Unity? Could you post the bug number if you have one.

[Russel]

Here is the Unity Forum Link:
http://forum.unity3d.com/threads/crash-occurs-in-kitkat-under-opengl-2-0.232643/

How do I get a bug number?

[chowon]

I had the same problem. No problem in OpenGL ES 3.0(in KitKat). OpenGL ES 2.0 only problem(in KitKat).
However, there are many devices that use OpenGL ES 2.0. That's why I can not build OpenGL ES 3.0.
This is a very serious issue that our development team.

[ArenMook]

Help -> Report a Bug

[gdeglin]

Just reported it myself. Case 618714 http://fogbugz.unity3d.com/default.asp?618714_cqbtk45pudo6t8if

My attempts to put together a test case have failed so far, so I pointed them at this thread and a few others threads about this issue I found on the Unity forum. If you don't mind submitting your project to Unity, please use the report a bug feature too and reference Case 618714.

[gdeglin]

Hey all. We might have a fix.

In UIDrawCall change:

1. #if !UNITY_4_3 || !UNITY_ANDROID
2.         // If the number of vertices in the buffer is less than half of the full buffer, trim it
3.         if (!trim && (verts.size << 1) < verts.buffer.Length) trim = true;
4. #endif
5.  

to

1. #if !UNITY_ANDROID
2.         // If the number of vertices in the buffer is less than half of the full buffer, trim it
3.         if (!trim && (verts.size << 1) < verts.buffer.Length) trim = true;
4. #endif
5.  

Let me know if this works for you!

[Russel]

@ArenMook Thank you!

@gdeglin We don't have a test device where the issue occurs. Thanks for your help!

[ArenMook]

This was supposedly fixed in Unity 4.5 according to version notes, so if that's not the case then Unity should certainly be made aware of the problem. The #if section @gdeglin mentioned was a hack around the problem, and it's not used in 4.5 as Unity said they fixed it.

[gdeglin]

Yep, that's the conclusion I reached too. Explains why the error went away and then came back though -- it was due to people upgrading to Unity 4.5.

We've been testing our game quite a bit and it seems stable now after the change. Hopefully someone else can test and confirm if this workaround fixes things through.

No response to my Unity bug ticket yet.

[Skjalg]

Any update from unity on this issue? We're experiencing crashes on xperia devices too. (using unity 4.5.2)