What Is Fatal Signal 6 in Android Logcat

What is fatal signal 6 in android logcat

Without more details (like seeing some code).

1) Do not block the UI thread, this can cause a SIGABRT as the OS will kill a non-responsive app.

bind and unbind on every activity when i switch for like 11 times it crashes my app

2) Make sure that in your OnDestroy within your Activity you are cleaning up after yourself. i.e. Removing all your Listeners/Events and then calling the Base.OnDestory.

3) An external (i.e. BluetoothLeService) service calling back into your app with listeners that now null/nil will cause hangs and thus a SIGABRT, see #2

Android app crashes with SIGABRT Signal 6 only while Eclipse debugging

android intentionally kills the process because it thinks the UI thread is hung, so its a ANR right.
for debugging purposes you can,

Go to Settings -> Developer options and check Show all ANRs.

This will show an App Not Responding dialog for apps running in the background. You can click the Wait button in the dialog to prevent the system from killing your process until the debugger attaches.
Note that the dialog is opened automatically for apps running in the foreground. For background apps, you have to enable this option

Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) at random times while operating with app

The problem was solved by replacing sliding_up_panel lib with native DraggableScrollableSheet

---

Related Topics