koobas.hobune.stream
Crash Fatal Exception signal 7 (SIGBUS) on Android 4.4
I've received a couple of strange crash reports of our game running on a MiPAD Android tablet. Both logs are the same, only changing register memory addresses.
Does somebody know if this is fixed in Unity 5.0.3 or even 5.1 ?
java.lang.Error: FATAL EXCEPTION [UnityMain]
Unity version : 5.0.2f1
Device model : Xiaomi MI PAD
Device fingerprint: Xiaomi/mocha/mocha:4.4.4/KTU84P/5.4.3:user/release-keys
Caused by: java.lang.Error: signal 7 (SIGBUS), code 1 (BUS_ADRALN), fault addr 76d5e26e
Build fingerprint: 'Xiaomi/mocha/mocha:4.4.4/KTU84P/5.4.3:user/release-keys'
Revision: '0'
pid: 6685, tid: 6701, name: UnityMain >>> [EDITED] <<<
r0 768afdf2 r1 fffff33a r2 00d800d7 r3 00000237
r4 0000011b r5 0cc60cc6 r6 0000011a r7 76d5e26e
r8 00000000 r9 76d5e26e sl 001145a0 fp 00000001
ip 76d5e26e sp 71350870 lr 768afdee pc 7042fbd4 cpsr 73753a33
at libunity.002dcbd4(Native Method)
at libunity.002e09c8(Native Method)
at libunity.002dc628(Native Method)
at libunity.00239fec(Native Method)
at libunity.001325b4(Native Method)
at libunity.0013302c(Native Method)
at libunity.00134540(Native Method)
at libunity.0013d694(Native Method)
at libunity.0014a340(Native Method)
at libunity.0014aef0(Native Method)
at libunity.00164c38(Native Method)
at libunity.00348d88(Native Method)
at libunity.00349f08(Native Method)
at libunity.004bc87c(Native Method)
at libunity.004c16bc(Native Method)
at libdvm.dvmPlatformInvoke(dvmPlatformInvoke:112)
at libdvm.dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)(dvmCallJNIMethod:398)
at libdvm.000267e0(Native Method)
at libdvm.dvmMterpStd(Thread*)(dvmMterpStd:76)
at libdvm.dvmInterpret(Thread*, Method const*, JValue*)(dvmInterpret:184)
at libdvm.dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)(dvmCallMethodV:336)
at libdvm.dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)(dvmCallMethod:20)
at libdvm.00054b63(Native Method)
at libc.__thread_entry(__thread_entry:72)
at libc.pthread_create(pthread_create:240)
Here are the specs of the tablet:
-NVIDIA Tegra K1 2,2 GHz Quad-Core
-192 NVIDIA CUDA / NVIDIA Kepler GPU
-2 GB RAM
-16 GB ROM
-Display 2048 x 1536 Pixel, 7,9 inch
This issue is fixed in Unity 5.0.3 patch 1.
Thank you, just found the fix in 5.0.3p1 release notes:
(700531) - Android: Fixed an issue whereby unaligned access caused a crash on Tegra $$anonymous$$1.
This does not seem to be fixed in 5.1.0f3, I am also getting the same crash on the same device.
Probably the fix is not included in 5.1.0f3. It seems 5.0 and 5.1 are in parallel development and fixes to the same bugs are merged into both versions.
You could try the newest patch release 5.1.1p1 from http://unity3d.com/unity/qa/patch-releases but I don't see the fix mentioned in the release notes.
Having same problem again with $$anonymous$$IPad(nvidia tegra k1) with 5.3.0. Upgraded to 5.3.2 problem remains. As it seems to me you can reproduce the situation following the steps (Happened to me when more than one sprite with Animation controller.)
Created 2D project
Add some background and foreground images (Works)
Add one animated character to the scene (Works)
Add second animated character to the scene (SIGBUS 7, Crash)
