Sure, but that's just masking the real problem, and is preventing the system from caching your application.
On Tue, Apr 7, 2009 at 9:48 PM, manohar <manohar...@gmail.com> wrote: > > Thanks, android.os.Process.killProcess(android.os.Process.myPid()); > this got worked for me > > On Apr 7, 9:25 pm, Marco Nelissen <marc...@android.com> wrote: >> You should start by taking a look at the system log to see what the >> actual problem is. There will probably be a helpful stack trace in >> there. >> >> >> >> On Tue, Apr 7, 2009 at 4:01 AM,manohar<manohar...@gmail.com> wrote: >> >> > Hi all, >> >> > I am unable to completely destory my app. My app is thread based app. >> > Once i exit the app by calling onDestroy method, it is exiting >> > properly. If i try to relaunch the application is says "The applicatin >> > stoped unexpectedly, try again". If i again select my app it is >> > launching. It means in a alternative attempt its launching. as i am >> > guessing, its not making Null for few static objects. once it shows >> > the exception has explained above it is making all the objects null, >> > so that i am able to reluanch. Pls can some one suggest how to >> > overcome this issue. How to completely destory the application?? >> >> > regards >> > manu- Hide quoted text - >> >> - Show quoted text - > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
