> If onDestroy() is not called, the process is being terminated, which > flushes all the process' threads along with it.
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? That is the behaviour I am seeing - if I don't terminate the threads in onDestroy(), they stick around after my application is destroyed. > That may be good for other reasons, such as not consuming CPU time > while your app is not in use. 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. Does the emulator have a way of terminating an application with no corresponding onDestroy()? -- 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
