The Dev Tools app on the emulator has an option that might help: > http://developer.android.com/intl/zh-CN/guide/developing/debug-tasks.html > Immediately destroy activities > Tells the system to destroy an activity as soon as it is stopped (as if > Android had to reclaim memory). This is very useful for testing the > onSaveInstanceState(Bundle) / onCreate(android.os.Bundle) code path, which > would otherwise be difficult to force. Choosing this option will probably > reveal a number of problems in your application due to not saving state.
On Mar 9, 7:40 am, qvark <[email protected]> wrote: > Hi, > > I'm having troubles with users that report that if they leave the > application opened and after a few hours when they return to it the > app crashes. I'm pretty sure it is because I'm not storing/restoring > the status correctly when my process is killed by the system, but I > would like to be able to test it in a repeatable way. > > Which is the best way to simulate the same behaviour that happens when > Android kills my process on low memory conditions? (killing the > process from the DDMS view, sending a signal from the adb, ...) > > Thanks, > > Jose Luis -- 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
