You can use "adb logcat -b events" to see the event log for what the activity manager is doing to try to understand what is going on. Also "adb shell dumpsys activity" will show you the current state of the activity stack (at the top of the output).
My guess is that you are getting a second instance of the activity being launched, with a different Intent. On Nov 6, 8:51 am, CJ <[EMAIL PROTECTED]> wrote: > according to the picture, for an regular activity, if onstop is called > and ondestory is not called, there are only two ways to go: oncreate > or onrestart. which means, if oncreate is called, the PROCESS is > killed. > > here is my application: the activity starts a thread that runs in th > background. then, i press the home key on the phone and click on my > application icon again. according to the debugger, th oncreate is > called which means the process has been killed. but, the debugger also > shows that the thread has never been killed which also means the > process has never been killed. > > does it suggest that the red box saying process is killed does not > necessarily happen every time? > > can anybody explain? > > thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
