On Mon, Oct 11, 2010 at 5:58 PM, A Curious Developer <[email protected]> wrote: > Excellent, I was worried for nothing. To be clear ... if onDestroy() > *does* get called, the threads are *not* terminated by the system and > I must terminate them myself?
Correct. You fork it, you clean it up. > Good point. I think I have that covered: onPause() puts all my threads > into a wait() that gets interrupted during onDestroy(). Destroying the > threads and recreating them is doable but complicated by needing to > recreate any pending messages for each thread. OK, so long as they're nice and quiet. > Does the emulator have a way of terminating an application with no > corresponding onDestroy()? You can use DDMS to terminate a process (see the stop button in the toolbar above the tree-table of devices and processes). -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
