> Also note that calling Activity.finish() doesn't actually quit the process, > so the OS is still in charge of managing when the process goes away.
That's why I am still using System.exit(0); at the end of onDestroy() to also kill the process, because my app somehow leaks memory from run to run, and I have been unable to track down the cause of this leaking - there is no leaking during a run, only across runs. I really wish there were some means to identify what is leaking where with the OS still in charge. Regards On Jan 28, 12:55 am, Marco Nelissen <marc...@android.com> wrote: > Having a UI element for the user to select that then causes > Activity.finish() to be called is no different from the user pressing the > back button. In fact, this is what Activity.onKeyDown() does when you let > the back key fall through. > Also note that calling Activity.finish() doesn't actually quit the process, > so the OS is still in charge of managing when the process goes away. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
