On Nov 18, 9:53 am, Dianne Hackborn <[email protected]> wrote: > On Wed, Nov 18, 2009 at 8:27 AM, jotobjects <[email protected]> wrote: > > Don't you care just as much about Activities that have threads running > > the background? > > No, the system can freely kill those processes when it needs memory. Thus > this isn't the cause of the main problem, the overall system becoming slow > because too much stuff is trying to run.
If the system is slow due to CPU contention then an Activity running in the background would also be part of the problem. If the system is low on memory the System can also kill Services. But I get it that too many Services thrashing has been the bigger problem. > The new running services UI > -only- stops a service, doesn't kill a process or anything else, because > that is all that is needed to free up that process to be available to the > system. So applications need to be coded to restart their own Services. It's even possible that the app's Activities are still running threads in the background but the Services have been stopped. Thanks for all the clarification - for the most part confirms what I understood. -- 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
