Question

I have a bug I’m trying to analyze that occurs when the Activity’s onDestroy() method is called after hitting the back button. I’ve put breakpoints in the offending code (using Eclipse). The debugger pauses the app at the breakpoint, but the Android system also takes the app off the screen and returns to the phone’s homescreen. After the app is paused for about 10 seconds, the app’s thread seems to get destroyed by the Android system because the debugger suddenly disconnects.

Any ideas on how to keep the Android system from doing this? I need to keep the app alive so I can step in the debugger, look at variables, etc.

Phone is running Android 2.3.5.

Answer 1

A workaround that I found is to put a startActivity() call into onDestroy() (before super.onDestroy()) that starts a dummy instance of the Activity, just to keep the app alive. The Android system won’t garbage collect the app thread because there is still an Activity running within it (the new dummy Activity). This in turn allows you to debug things because the debugger’s connection to thread won’t be lost.

If the phone pops up a dialog saying the app is not responding (Force Close or Wait), don’t click Wait, just leave it alone. It seemed that clicking Wait caused the app thread to be killed and a new thread was created for the dummy Activity.