After reading the Android Activity documentation, I'm still a bit confused on Activity Lifecycles. Clarification on the two points below would be greatly appreciated.
When the system is running low on memory, can it selectively choose to destroy an activity in the process, instead of the entire process? For example, if a process has a service and a non-visible activity running within, does the OS destroy only the activity, letting the process with the service continue to live? Or, should I assume that when the OS destroys an activity, it destroys the entire process? Also, when an activity is destroyed (either by calling finish() or by the system), does everything get GC'd regardless if the variables are public, private, static, etc? Thanks in advance. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
