Ironically, it wasn't that I was overreleasing something but rather that I was under releasing. Specifically, the fetchedResultsController's delegate was a view controller. The view controller owned the fetchedResultsController. Presumably a fairly common pattern. However, the view controller's dealloc didn't release the fetchedResultsController, so when the data changed, it was still observing it and tried to the tell its delegate.
I'm a little surprised that the view controller was dealloced as it was still on the navigationController stack (one below the current view). Reading about the navigation controller now... On 26/12/2009, at 01:29 , Kyle Sluder wrote: > On Dec 25, 2009, at 12:48 AM, Brian Bruinewoud <br...@darknova.com> wrote: > >> *** -[NSCFType controllerDidChangeContent:]: unrecognized selector sent to >> instance 0x3a11d70 > > Usually this is a sign of a memory management error, specifically an > overrelease. Run with zombies enabled to find it. > > --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
