No because I don't believe onDestroy would necessarily get called backing out of the activity. Only onPause would be guaranteed to be called. That activity's onDestrw would only get called at some random point in the future when the OS wants more memory.
OnPause is the primary. At least that is my understanding. I hope someone corrects me. On Mar 19, 3:37 pm, lbendlin <l...@bendlin.us> wrote: > If one activity calls another, and when you then press "Back" from that > activity, wouldn't the calling of onDestroy() assure you that the called > activity is truly gone and the memory is freed? (Or conversely, if it isn't > called, the activity may live on due to dangling references?) -- 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
