Hello,

Most of the time, an uncaught exception on the main (UI) thread will result 
in Android showing a dialog saying something along the lines of 
"Unfortunately, [app] has stopped", with an "Ok" button which when pressed 
kills the process.

Sometimes, however, this dialog is not shown, and the process does not get 
killed by Android. Instead, the application remains in an error state where 
e.g. broadcast receivers no longer receive messages.

In both cases, the stack trace for the uncaught exception is printed in the 
logs. The only difference in the log output between the two cases is than 
in the former, I get a log entry saying "Sending signal. PID: [pid] SIG: 9".

This latter case is a problem for me because my app has several broadcast 
receivers (for GCM and alarms) that I would like to remain functional after 
an activity has crashed. Otherwise there is no way for the application to 
recover except for the user manually restarting the application or 
rebooting the device.

I'm thinking of working around this by defining an UncaughtExceptionHandler 
which then takes care of killing the process, but I'd like to better 
understand the situation before taking this step.

Can anybody shed some light on why and when this second case may happen? Or 
point me to the relevant docs? So far it seems to happen when the crash is 
triggered by broadcast receivers, but this is difficult for me to get a 
handle on.

Any suggestions would be much appreciated!

Thanks,
Michael

-- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
To post to this group, send email to android-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/android-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-developers/d5fb1466-ac8f-4f65-9004-5cf248fd03f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to