[android-developers] Re: Binder is leaked by binding to a service

2010-08-05 Thread Mogimo
Thank you for your kind reply! On 8月2日, 午後9:12, brucko geoff.bruck...@gmail.com wrote: Sorry for slow reply - been away. By the way, if I changed LocalBinder to a static inner class, does it make sense ? I have made a separate generic class that usually use for all my services ie one

[android-developers] Re: Binder is leaked by binding to a service

2010-08-02 Thread brucko
Sorry for slow reply - been away. By the way, if I changed LocalBinder to a static inner class, does it make sense ? I have made a separate generic class that usually use for all my services ie one that I import in - just a bit of cut and paste. That way I can reuse the code for all my

[android-developers] Re: Binder is leaked by binding to a service

2010-07-31 Thread Mogimo
Thank you for your information!! I will keep watching it out. By the way, if I changed LocalBinder to a static inner class, does it make sense ? That means to return back the same binder for all connections? On 7月31日, 午前5:24, brucko geoff.bruck...@gmail.com wrote: This appears to be a bug

[android-developers] Re: Binder is leaked by binding to a service

2010-07-30 Thread Brion Emde
Binding to a service is asynchronous. You should maybe disable the button that binds and unbinds until you are sure that you are actually, respectively, bound and unbound. You do that by keeping track of when the ServiceConnection object's onServiceConnected() and onServiceDisconnected()

[android-developers] Re: Binder is leaked by binding to a service

2010-07-30 Thread brucko
This appears to be a bug http://code.google.com/p/android/issues/detail?id=6426 watch out. If your LocalBinder is a non-static inner class, then you will leak your Service as well as non-static inner classes have a reference to the outer class. -- You received this message because you are