Search Issue Tracker

Not Reproducible

Votes

50

Found in

4.6.0f3

Issue ID

655263

Regression

No

Android crash: Fatal signal 11 (SIGSEGV) on some devices

Android

-

On a small number of Android devices app crashes having exhibited very strange behaviour. The behaviour can vary but the result is (almost) always "Fatal signal 11 (SIGSEGV)"
Log in to vote on this issue

Comments (78)

  1. jjennings1990

    Mar 04, 2017 00:19

    I'm getting this issue on Unity 5.6b9 when Utilizing Pointer Event Overrirdes or the Trigger events related to Pointers on my Google Pixel phone .

    It crashes both the editor and the app on the device

  2. suatwixot

    Feb 13, 2017 12:25

    We are suffering because of this bug

  4. elmortem

    Jan 18, 2017 10:32

    Have same crashes.

  5. Cuicui_Studios

    Jan 17, 2017 10:52

    Same here!!!

  6. SioHio

    Jan 13, 2017 07:10

    java.lang.Error: FATAL EXCEPTION [main]
    Unity version : 5.4.3f1
    Device model : samsung SM-G930T
    Device fingerprint: samsung/heroqltetmo/heroqltetmo:6.0.1/MMB29M/G930TUVU4APK1:user/release-keys

    Caused by: java.lang.Error: signal 6 (SIGABRT), code -6 (?), fault addr --------
    Build fingerprint: 'samsung/heroqltetmo/heroqltetmo:6.0.1/MMB29M/G930TUVU4APK1:user/release-keys'
    Revision: '14'
    pid: 11958, tid: 12131, name: Thread-5992 >>> com.test.abc <<<
    r0 00000000 r1 00002f63 r2 00000006 r3 d4459978
    r4 d4459980 r5 d4459930 r6 00000000 r7 0000010c
    r8 00000043 r9 f427de44 sl d3b5a5bb fp f4263d10
    ip 00000006 sp d4458d18 lr f6f3b12d pc f6f3d528 cpsr 4d4d2f31

    at libc.tgkill(tgkill:12)
    at libc.pthread_kill(pthread_kill:32)
    at libc.raise(raise:10)
    at libc.__libc_android_abort(__libc_android_abort:34)
    at libc.abort(abort:4)
    at libc.abort(abort:4)
    at libc.abort(abort:4)
    at libc.abort(abort:4)
    ...

  7. Ibexgames

    Jan 05, 2017 06:12

    App crashes randomly after updating Unity to 5.5. Please reopen

    Fatal Exception: java.lang.Error: FATAL EXCEPTION [UnityMain]
    Unity version : 5.5.0p2
    Device model : samsung SM-J320P
    Device fingerprint: samsung/j3ltespr/j3ltespr:5.1.1/LMY47X/J320PVPU1APH2:user/release-keys

    Caused by java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
    Build fingerprint: 'samsung/j3ltespr/j3ltespr:5.1.1/LMY47X/J320PVPU1APH2:user/release-keys'
    Revision: '7'
    pid: 7501, tid: 7539, name: UnityMain >>> game bundle id <<<
    r0 b823453c r1 00000007 r2 00000000 r3 00000000
    r4 a08ccdbb r5 b8233350 r6 b81e6370 r7 ffffe97c
    r8 000011ec r9 00000000 sl 00000002 fp 00000002
    ip 0000002a sp 9f8c08a0 lr ffffffff pc 9feccdec cpsr 4a2f5837

    at libunity.0050ddec(Unknown Source)
    at libunity.002190d8(Unknown Source)
    at libunity.001de06c(Unknown Source)
    at libunity.00233258(Unknown Source)
    at libunity.0053c80c(Unknown Source)
    at libunity.0053c4c4(Unknown Source)
    at libunity.0053eda8(Unknown Source)
    at data@app@net.00600ef7(Unknown Source)

  9. MayhemMike

    Oct 23, 2016 21:20

    same here with Unity 5.4.2f1 pls reopen

  10. pravusjif

    Sep 30, 2016 16:12

    I'm having the same error on a Moto X, using Unity 5.3.4.

    At the beginning of the app I'm playing a video using Handheld.PlayFullScreenMovie() and loading a level aftwerwards, and after that video I get the crash on that device.

    So I just added an additional yield return new WaitForSeconds(0.5f); after the 2 common yield return new WaitForEndOfFrame(); I use in the coroutine that triggers the video.

    This extra waiting probably lets the device close the video display correctly, and thus avoiding the error. I'm guessing this is being triggered when trying to load another level and not having stopped correctly a previous routine/process/somethingLikeThat.

    http://pastebin.com/Px5j5fic

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues