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
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)"
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- GPU utilization increases by 20% on Meta Quest headsets when Render Graph is enabled on 6000.0.16f1 and higher
- Value on Slider (Int) control in UI Builder displays as default when saving UI Document
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
- Non-HDR color picker opens when selecting material color with HDR enabled
Timberoth
Sep 02, 2015 16:55
We're still running into this issue on a HTC M8 One with Unity 4.6.7p2
doppelmonster
Aug 12, 2015 16:27
the sigsegv 11 error occured to my project after upgrading the project from 4.5 to 5 (up to 5.0.2) on nexus s device.
Now its gone after updating to 5.1.2 (from 5.0.2)!
Maybe related: I am also using lots of mobile particle materials (mostly "multiply" not sure if i use "alpha blended" as well) maybe "sebek89" repro case was my problem as well.
For me its fixed with the update!
sebek89
Jun 26, 2015 13:14
Forgot to add that for that repro it happenes on all devices (different GPU vendors) I've tested this (Sony Xperia Z, Galaxy S4, Lenovo A820, Acer Iconia A1-810).
sebek89
Jun 26, 2015 13:13
I have 100% repro for that crash, even on latest 5.1.1p1:
1) Create material with Particle/Alphablended or Mobile/Particle/Alphablended
2) Attach this material to normal model (even built-in cube)
3) Place two or more such objects on the scene
4) Enable dynamic batching
Result: crash on android device.
If you change the shader or disable dynamic batching the crash doesn't occur. Please fix that ASAP!
MinhDao
Jun 23, 2015 11:18
Still happening in 5.0.1f1 (zenphone 5)
MadMonkey119
Jun 13, 2015 03:31
Still happening to me on 5.0.1f1
Rienhl
Jun 11, 2015 16:19
Still happening in 4.6.6
BenouKat
Jun 04, 2015 14:13
Still here in 5.0.1f1. Constant crash on Android Lollipop.
chaostheorygames
May 27, 2015 01:54
Just seen this crash on a brand new Galaxy Note 4 with Lollipop 5.0.1 building with Unity 5.0.1f1. Works fine on our other test devices (Xperia Z2, Nexus 7 [original], Galaxy S4 and Note 8).
Have tried changing OpenGL settings and checking / unchecking 32-bit display buffer in Android Player Settings but no luck.
adb output before crash:
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x1f9e4ff8
r0 00004500 r1 00000000 r2 00004500 r3 b6c3a138
r4 00004500 r5 00000000 r6 92fe2000 r7 9a64dfb0
r8 00000001 r9 00000001 s1 00000001 fp af678fe0
ip 00000012 sp af9e5008 lr b6c316e0 pc b6c358bc cpsr 800d0030
backtrace:
#00 px 000018bc /system/lib/libGLESv1_CM.so
#01 pc 000016dc /system/lib/libGLESv1_CM.so
jptsetung
May 19, 2015 20:05
Just seen this crash on a game compiled with v5.0.1p4 on a Xperia Tablet Z (SGP311).
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
r0 00000001 r1 40087f24 r2 00000001 r3 0000001d
r4 00000000 r5 416ae8d0 r6 e82d7a83 r7 415eecf8
r8 000159fa r9 415eecf0 sl 416ae8e0 fp be99839c
ip 76c2b6c8 sp be998370 lr 76163b54 pc 76164b04 cpsr 80010010