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
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
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.