I think there is going to be updating of the user documentation to better explain this. The current SDK documentation I think is relatively clear about there being empty processes (the last process bucket) that can be hanging around.
On Mon, Feb 8, 2010 at 11:25 PM, Al Sutton <[email protected]> wrote: > Thanks for the clarification Dianne. > > I'm guessing the confusion comes from people who (like me) are > familiar with the traditional Linux process model of when a process > has finished it dies and aren't expecting a garbage collecting process > management system :). > > I'd read the process/threads section you've mentioned and in my mind > it read as a warning of what could happen if resources become tight as > opposed to it being the expected normal operation for all processes. > Might it be worth adding a line that explicitly states that it is > normal for processes to be left running when there they are not active > and will only be killed off if resources become constrained enough for > it to be necessary? > > Thanks again, > > Al. > > On Feb 8, 8:23 pm, Dianne Hackborn <[email protected]> wrote: > > Yeah hopefully it is a positive impact. > > > > Developers really shouldn't have to explain this, and I am very sorry you > > are being put into this position. I don't really understand why users > would > > pick out some applications to complain about, when every single one > > (including the ones built into the platform) works this way. > > > > > > > > > > > > On Mon, Feb 8, 2010 at 12:04 PM, Bob Kerns <[email protected]> wrote: > > > Actually, I believe you should go further, and say it has a POSITIVE > > > impact on the user. > > > > > It takes time to tear down and recreate a process that may be reusable > > > a short time later. And Android can possibly do the teardown at a less > > > busy moment. > > > > > The only downside I see is that we developers will have to learn to > > > explain this to users who think we're being sloppy. > > > > > -- > > > 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]<android-developers%[email protected]><android-developers%2Bunsubs > [email protected]> > > > For more options, visit this group at > > >http://groups.google.com/group/android-developers?hl=en > > > > -- > > 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]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- 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
