In a low memory situation Android can shut down apps and has some
logic to prioritize which apps to shut down first. I have read some
comments that Android can also partially destroy an app by destroying
Activities that are not currently used. Since I haven't found any
documentation about this, I
The docs says this:
http://developer.android.com/guide/topics/fundamentals/activities.html#Lifecycle
If an activity is paused or stopped, the system can drop it from memory
either by asking it to finish (calling its |finish()| method), or simply
killing its process.
IIRC, the emulator has
On Sun, Jul 10, 2011 at 11:47 AM, Kostya Vasilyev kmans...@gmail.com wrote:
IIRC, the emulator has a setting / button somewhere to trigger the
destruction of unused activities without killing the process, so there is a
way to test this case.
IIRC, that setting is in the Dev Tools app.
--
It will only destroy activities if you have a large number of them on your
stack. In practice, I think most apps will hit an out of memory error on
their local heap before encountering this (and don't have significantly deep
stacks), so are unlikely to encounter it.
On Sun, Jul 10, 2011 at 8:17
4 matches
Mail list logo
