Search Issue Tracker
Fixed in 5.3.5
Votes
1
Found in
5.3.1p4
Issue ID
765744
Regression
No
Fatal signal 11 (SIGSEGV), code 2 crash on Android devices
Some apps crashes with Fatal signal 11 (SIGSEGV), code 2 message on Android devices
Comments (3)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
V-Jankaitis
Dec 01, 2016 13:42
Still in 5.5 on Location.start() Android
t-schulz
Sep 09, 2016 08:44
Got that Signal 11 Crash with Code 1:: http://forum.unity3d.com/threads/e-crash-signal-11-sigsegv-on-some-android-devices.430093/
Still in Unity 5.4
darkForester
Feb 14, 2016 15:27
Same as this issue: https://issuetracker.unity3d.com/issues/ios-android-crash-after-multiple-scene-loads-fatal-signal-11-sigsegv-code-1
Please head over to vote.