> Further information: I have just gone through every place in our code where > it makes reference to the managed object context (there's only 90 of them > thank goodness), and there is nothing there where we either retain or release > a managed object context, or use one in a notification or anything like that. > > I have also found out that the managed object context that is over-released > is not the one that I have in my persistent document, so all I can assume is > that it is one that is created behind the scenes programmatically during the > persistent store migration. > > I also checked our will/didTurnIntoFault and awakeFromInsert/Fetch to make > sure they were clean. Found a few minor problems, but it made no difference. > I did find that awakeFromFetch was called during the process of migration, > but didn't find out anything else of interest. I also checked for description > methods that may have caused faults to fire at the wrong time. I only found > one description on one of our managed object classes, and an interesting > thing happened when I commented that out - I could not save at all (trying to > send an objectID message to an NSNumber). I have not tracked that one down > yet.
Try running with MallocStackLoggingNoCompact=1 set in the env and using malloc_history to see where an NSManagedObject was allocated and then freed and replaced with an NSNumber. - Ben _______________________________________________ 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
