If you press back and let the system finish the activity, all references to it will be gone, so though your process is there after it GCs the resources (views etc) associated with the activity should be gone. If you still see them after you know the process has GCed, then you have a leak in your app.
On Thu, Oct 15, 2009 at 7:57 AM, String <[email protected]>wrote: > > On Oct 15, 3:08 pm, Mika <[email protected]> wrote: > > > So the problem is quite simple. I start a Service from an Activity, > > the user presses back, the Activity goes away and the Service stays > > running in the background. However the activity (and it's views) still > > stay in memory. > > Feature. It's central to the Android architecture that activities > aren't killed by the system until their resources are needed > elsewhere. The idea, I think, is that if the user goes back into your > activity before that happens, it's ready and waiting. > > Some good discussion of it in this thread: > > http://groups.google.com/group/android-developers/browse_thread/thread/fc97b4359f5c7880 > > String > > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
