2009/10/2 José Prieto Garay <[email protected]> > I think this is the point, normally when our application needs to be > destroyed in order to release memory, or it's in a lower priority then > onDestroy() is called. >
That is not true. If the user presses home, they will leave your app, it will go in the background, and onDestroy() will not be called. If you have left a service running, it is still in the background, and it is running, onDestroy() has not been called, but the system could very well kill it anyway when under memory pressure (which you will see a lot on devices like the G1 or myTouch). > With this "Force Stop" stuff not, there isn't any way to be aware > about our threads and tasks to be killed. > So how is this any different from a user going to the windows task manager and force killing an app? Or your application crashing while it is running? Or it ANRing and the user deciding to kill it? Or the user pulling the battery from their device? Or a desktop machine losing power? I don't think any of these things should leave an application in a bad state it can't recover from. -- 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 -~----------~----~----~----~------~----~------~--~---
