The activity manager does not remove activities based on their size. The kernel kills processes based on their current state (foreground/ background) and the overall memory available in the system, but the activity manager remembers their frozen state so that when the user returns to an activity in the killed process, a new process can be created and the activity restarted with its previous state.
Unless otherwise specified, all activities in a .apk run in their own, dedicated process, so they will all be killed together. I don't know why you would be seeing the behavior you are describing. On Mar 31, 6:53 am, Chris D <[EMAIL PROTECTED]> wrote: > In my application, almost all of my activities will return all the way > back to the main activity. Only two will not. Those are two rather > heavy activities. I'm watching the ActivityManager kill off the main > activity after I launch those two heavy activities. Is this by design? > Should I start putting "return to home" menu options in all my > activities? --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
