Thanks for the bug report. If you could see rdar://10109782, you'd see that your report prompted a new discussion about the priority and schedule for this bug.
On Apr 24, 2014, at 4:09 PM, Roland King <r...@rols.org> wrote: > "Engineering has determined that your bug report (16683382) is a duplicate of > another issue (10109782) and will be closed." > > .. that wasn't very worthwhile was it. > > On 22 Apr, 2014, at 12:49 pm, Roland King <r...@rols.org> wrote: > >> There you go. 16683382 >> >> On 22 Apr, 2014, at 2:55 am, Greg Parker <gpar...@apple.com> wrote: >> >>> 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. _______________________________________________ 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
