Well, there is exactly one place where the code binds and exactly one place where it unbinds. The binding is shared between the activities activity 1 does a bind on create and unbind on destroy.
Breakpoints and logging indicate that exactly one bind is called and no unbinds are called during the sequence that produces the leak. I am guessing that either it's an incorrect warning or there is some automatic machinery that I'm not aware of. mike
-- 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
