I think the system may sometimes keep empty apps's processes around in case the user goes back to them - unless it needs the memory of course.
Presumably any threads in such a process would be waiting for instruction - ie, called a binder ioctl which hasn't returned yet (and might never do so, if the process gets killed rather than restarted. If you start up a bunch of other memory hungry apps or use an emulator with a small memory size, does the process go away? On Sep 21, 5:36 am, Laurent Lugon <laurent.lu...@gmail.com> wrote: > Hi, > > I'm running an application with different activities. When I close my app, > all the activities are destroyed but my app still locked in my main thread > in: Object.wait(long,int) line : not available [native method] > Is there a service still running or something like that ? What can I do in > order to close properly my app ? > > Thanks ! > > -- > > SECU4 SA > Laurent Lugon Moulin > > Technical & Development Assistant > Technopôle 3 > 3960 Sierre – Switzerland > > Office : +4127 4567 931 > Fax : +4127 4567 > 935 > Mobile : +4179 4509 566 > > Skype : laurent.lugon.moulin > > www.secu4.com -- 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
