On Tue, May 25, 2010 at 6:14 AM, Gideon King <gid...@novamind.com> wrote: > An instance 0x11d0ce4b0 of class NMGeneralPrintAccessoryController was > deallocated while key value observers were still registered with it. > Observation info was leaked, and may even become mistakenly attached to some > other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the > debugger. Here's the current observation info: <all my observers> > > But I have put a breakpoint on my dealloc method, and in there, I do > deregister for those notifications. Dealloc is called, and I did check that > it was the same object, and all the calls to deregister are there. So I don't > know how it could *not* be removing the observers.
This sounds off… you're deregistering obeservers in your observee's -dealloc? It sounds like object A has observed object B, and object B is being dealloced, which is removing its observation on object C, but the framework is complaining about object A. --Kyle Sluder _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
