I’m developing android applications for a while, and followed a lot of posts about activity life cycle, and application’s life cycle.
Activity.finish() method calls somewhere in the way to
Activity.onDestroy(), and also removing the activity from stack, and I guess it somehow points to operating system and garbage collector that he can “do his trick” and free the memory when it find it a good time doing so….
I came to this post –
Is quitting an application frowned upon? and read Mark Murphy’s answer.
It made me a bit confused about what exactly the
finish() method actually does.
Is there a chance I’ll call
onDestroy() won’t be called?
finish() on an activity, the method
onDestroy() is executed. This method can do things like:
- Dismiss any dialogs the activity was managing.
- Close any cursors the activity was managing.
- Close any open search dialog
onDestroy() isn’t a destructor. It doesn’t actually destroy the object. It’s just a method that’s called based on a certain state. So your instance is still alive and very well* after the superclass’s
onDestroy() runs and returns.Android keeps processes around in case the user wants to restart the app, this makes the startup phase faster. The process will not be doing anything and if memory needs to be reclaimed, the process will be killed