On Apr 20, 2014, at 3:40 PM, Roland King <r...@rols.org> wrote: > If however one of A or B happens to be KVO'ing the other, which happens a lot > in my code, I use KVO everywhere, Leaks doesn't find the cycle. That's wrong, > KVO doesn't make a strong reference, as you can tell from the 'freed when KVO > was still attached to it' message, however it trips up Leaks. My handwaving > belief is that KVO information is kept in a separate table somewhere and the > Leaks process sees the A or B pointer in that memory and conservatively > assumes the objects are referenced. I should probably file a but one day.
Please file a bug report. Disguising pointers in side tables so leaks doesn't see them is routine. -- Greg Parker gpar...@apple.com Runtime Wrangler _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
