- Home /
Game crashes in some Android devices with Unity 4.6.1
Our game crashes in certain Android models, using the latest version of Unity. It worked ok compiling with versions previous to Unity 4.3. It works ok also for iOS and PC. The crash occurs every time, depending on the compilation it can occur in the logo screen or after starting a new scene.
The problem has been reproduced in the following devices:
Samsung Galaxy S3
Samsung Galaxy S4
Samsung Galaxy S5
Galaxy S3 Mini
Galaxy S5 Mini
Xperia Z2
Xperia Z3
Xperia Tablet Z
Here you can see the log:
12-02 10:13:22.483: A/mono(3248): * Assertion: should not be reached at mini-trampolines.c:183
12-02 10:13:22.483: A/libc(3248): Fatal signal 11 (SIGSEGV) at 0x00000cb0 (code=-6), thread 3327 (UnityMain)
12-02 10:13:22.493: A/mono(3248): * Assertion at mini-trampolines.c:535, condition `*vtable_slot' not met
12-02 10:13:22.543: W/qdhwcomposer(277): Excessive delay reading vsync: took 664 ms
12-02 10:13:22.564: I/DEBUG(11607): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-02 10:13:22.564: I/DEBUG(11607): Build fingerprint: 'samsung/jfltexx/jflte:4.4.2/KOT49H/I9505XXUGNG8:user/release-keys'
12-02 10:13:22.564: I/DEBUG(11607): Revision: '11'
12-02 10:13:22.564: I/DEBUG(11607): pid: 3248, tid: 3327, name: UnityMain »> com.dearfear.fistofjesus «<
12-02 10:13:22.564: I/DEBUG(11607): signal 11 (SIGSEGV), code -6 (SI_TKILL), fault addr 00000cb0
12-02 10:13:22.914: W/EDMNativeHelper(266): EDMNativeHelperService is published
12-02 10:13:22.954: I/DEBUG(11607): r0 00000000 r1 00000cff r2 0000000b r3 00000000
12-02 10:13:22.954: I/DEBUG(11607): r4 0000000b r5 0000000b r6 00000cff r7 0000010c
12-02 10:13:22.954: I/DEBUG(11607): r8 855acc7c r9 83775050 sl 8190dfa0 fp 78d7de84
12-02 10:13:22.954: I/DEBUG(11607): ip 87513e50 sp 78d7de50 lr 4004c18d pc 4005b134 cpsr 000f0010
12-02 10:13:22.954: I/DEBUG(11607): d0 0000000000000000 d1 0000000000000000
12-02 10:13:22.954: I/DEBUG(11607): d2 0000000000000000 d3 0000000000000000
12-02 10:13:22.954: I/DEBUG(11607): d4 402fed1000000000 d5 eb000000e51d1008
12-02 10:13:22.954: I/DEBUG(11607): d6 4099b80000000000 d7 0000000000000000
12-02 10:13:22.954: I/DEBUG(11607): d8 402ed1f141768f8c d9 0000000000000000
12-02 10:13:22.954: I/DEBUG(11607): d10 0000000000000000 d11 0000000000000000
12-02 10:13:22.954: I/DEBUG(11607): d12 0000000000000000 d13 0000000000000000
12-02 10:13:22.954: I/DEBUG(11607): d14 0000000000000000 d15 0000000000000000
12-02 10:13:22.954: I/DEBUG(11607): d16 747265737341202a d17 6d207461206e6f69
12-02 10:13:22.954: I/DEBUG(11607): d18 6d6172742d696e69 d19 2e73656e696c6f70
12-02 10:13:22.954: I/DEBUG(11607): d20 63202c3533353a63 d21 6e6f697469646e6f
12-02 10:13:22.954: I/DEBUG(11607): d22 6c626174762a6020 d23 2027746f6c735f65
12-02 10:13:22.954: I/DEBUG(11607): d24 3fd1b10853a79915 d25 3fd554fa9ca0567a
12-02 10:13:22.954: I/DEBUG(11607): d26 3fdb6db71408e660 d27 3fe33333332d4313
12-02 10:13:22.954: I/DEBUG(11607): d28 3ff0000000000000 d29 0000000000000001
12-02 10:13:22.954: I/DEBUG(11607): d30 fff0000000000000 d31 ffffffff00000000
12-02 10:13:22.954: I/DEBUG(11607): scr 80000013
12-02 10:13:22.964: I/DEBUG(11607): backtrace:
12-02 10:13:22.964: I/DEBUG(11607): #00 pc 00022134 /system/lib/libc.so (tgkill+12)
12-02 10:13:22.964: I/DEBUG(11607): #01 pc 00013189 /system/lib/libc.so (pthread_kill+48)
12-02 10:13:22.964: I/DEBUG(11607): #02 pc 0001339d /system/lib/libc.so (raise+10)
12-02 10:13:22.964: I/DEBUG(11607): #03 pc 002b8e00 /data/app-lib/com.dearfear.fistofjesus-1/libmono.so
12-02 10:13:22.964: I/DEBUG(11607): #04 pc 002b8f08 /data/app-lib/com.dearfear.fistofjesus-1/libmono.so
12-02 10:13:22.964: I/DEBUG(11607): #05 pc 002b8f64 /data/app-lib/com.dearfear.fistofjesus-1/libmono.so
12-02 10:13:22.964: I/DEBUG(11607): #06 pc 000efeb4 /data/app-lib/com.dearfear.fistofjesus-1/libmono.so
12-02 10:13:22.964: I/DEBUG(11607): #07 pc 00002054
12-02 10:13:22.964: I/DEBUG(11607): stack:
12-02 10:13:22.964: I/DEBUG(11607): 78d7de10 00000000
12-02 10:13:22.964: I/DEBUG(11607): 78d7de14 00000000
12-02 10:13:22.964: I/DEBUG(11607): 78d7de18 00004000
12-02 10:13:22.964: I/DEBUG(11607): 78d7de1c 841a2cf8
12-02 10:13:22.964: I/DEBUG(11607): 78d7de20 78d7de4c [stack:3327]
12-02 10:13:22.964: I/DEBUG(11607): 78d7de24 00000037
12-02 10:13:22.964: I/DEBUG(11607): 78d7de28 ffff4208
12-02 10:13:22.964: I/DEBUG(11607): 78d7de2c 841a2cb0
12-02 10:13:22.964: I/DEBUG(11607): 78d7de30 0000007f
12-02 10:13:22.964: I/DEBUG(11607): 78d7de34 7babbee0
12-02 10:13:22.964: I/DEBUG(11607): 78d7de38 78d7de4c [stack:3327]
12-02 10:13:22.964: I/DEBUG(11607): 78d7de3c 78d7de4c [
Any advise?
Black screen after run on device (Huawei U8800 Android 4.0.3) or emulator Android 4.0.4. No show Unity splash screen. In Unity 4.6.0 all work, but in 4.6.1 not work. Why?
I have an Acer A500 with Android 4.0.3 that no longer runs after updating to 4.6.1.
Black screen after run on device, i'm using Samsung Galaxy S2 with Unity 4.6.1.
I have the same problem with Galaxy Tab 2 (10.1) GT P-5100 In Unity 4.6.1f1. I made an empty project to test it, all settings set to recommended on this page. Even tried turning off Vsync. Seems to be a problem in Unity.
Answer by Bunny83 · Dec 10, 2014 at 06:46 PM
Since you have perfect detailed information about the issue you should file a bug report in Unity (Help -> Report a Problem). Make sure you include the example project that reproduces the problem and include your logcat as well as the description of the problem (including the devices which causes problems).
From what we can see in the logcat it seems to be a mono issue.
ps There's just another crash-issue over here so keep your eyes open for solutions ^^. If you get any informations from Unity please post an answer to this question.
pps: I can't stand those developers that insert asserts like "should not be reached"... Very helpful...
Answer by Umresh · Dec 26, 2014 at 06:20 AM
Had the same problem try the patch 4.6.1p2.
I had the same issue as others have described. $$anonymous$$y Acer a200 would crash on startup with Android builds. Test on $$anonymous$$otoX and it worked fine. After updating to 4.6.1p2 my builds worked perfectly!
Answer by meat5000 · Dec 10, 2014 at 02:52 PM
I believe the Devices listed all contain Adreno GPU. This may be relevant. Searches for this crash suggest a problem with OpenGL compatibility in some way.
Start by switching off VSync.
Answer by Andreyvtr · Dec 13, 2014 at 09:07 AM
Patch 4.6.1p1 fixed this problem on my device Huawei U8800 pro (Android 4.0.3) and in emulator 4.0.4.
Answer by niebau · Dec 16, 2014 at 07:54 AM
Two of my customers reported black screen / crash problems right after starting one of my games (Samsung Galaxy S2 with Android 4.x and a Nexus 7 with Android 5.0). Happened for both Unity 4.6 and Unity 4.6.1. Going back to Unity 4.5.5 finally fixed the issue on both devices.
I couldn't reproduce the problem on my own Galaxy S2, unfortunately. So I can't shed some further light on this issue, I'm afraid (e.g. crash log).