We have been trying to port the Android version of our Golf App to Unity 5 but have had trouble with a high frequency seemingly random crash every time we release our product to production forcing us to revert to Unity 4. We do not have a repeatable case and in fact have been unable to get this crash to occur in house.
The crash:
- Affects about 5% of our users according to Crittercism
- Does not seem to be related to a specific device, brand of devices or OS version
- Has no symbol information other than a at libunity.00380e54(Native Method) – complete stack below
We have experienced this crash on 5.2.3p3 and 5.3.1p2 but we don’t experience it on 4.6.8p1. What version of Unity are folks currently using for Android and for those who run Crittercism or Crashlytics how stable are they?
Stack Trace
0 java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000018
1 Build fingerprint: ‘samsung/d2spr/d2spr:4.4.2/KOT49H/L710VPUDOH1:user/release-keys’
2 Revision: ‘14’
3 pid: 2784, tid: 2852, name: UnityPreload >>> com.wgt.android.golf <<<
4 r0 00aad910 r1 00000120 r2 00000001 r3 00000b24
5 r4 645c74d8 r5 00000b61 r6 00000000 r7 00000000
6 r8 000003cb r9 63058a90 sl 00000002 fp 63ab9c40
7 ip 00000001 sp 63ab9c30 lr 40115d15 pc 61fbf6c4 cpsr 55505630
8
9 at libunity.004036c4(Native Method)
10 at libunity.003fec8c(Native Method)
11 at libunity.003db2d8(Native Method)
12 at libunity.003d9ca0(Native Method)
13 at libunity.003d9bf0(Native Method)
14 at libunity.00433d9c(Native Method)
15 at libc.__thread_entry(__thread_entry:72)
16 at libc.pthread_create(pthread_create:240)
It seems unlikely if this is a problem with Unity that we are the only ones experiencing it unless our code is doing something that causes it to manifest. Does anyone know of a method to get better symbols for the libunity addresses above? If we knew more about the crash, we might be able to isolate it down to a repeatable case.