On Mon, Feb 14, 2011 at 3:10 PM, Kevin Duffey <[email protected]> wrote:
> I am curious why if in your onDestroy you shut down any tasks/threads, your
> app would still show up? I would think it would exit properly if you wanted
> it to. Perhaps I misunderstood that. I thought if the lifecycle onDestroy
> fires, that meant your app (or at least the activity) was going to be done.
> If you only have one activity then your app should essentially close. If
> your app is made of multiple activities, then calling finish() does that not
> end the activity? Assuming you have 3 or 4 running, and you call that on all
> of them, wouldn't your app shut down?

"The app" is a basked of components, hosted by a process.

Components come and components go. However, if there are no components
right now, Android may still hang onto the process, in case something
happens momentarily that causes another component to show up.
Eventually, Android will terminate a component-less process, to free
up RAM for use by other processes.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

Android Training...At Your Office: http://commonsware.com/training

-- 
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

Reply via email to