I have a CoreData app I've been working on for months, and I'm
encountering a problem that appears to be caused by CoreData caching
behavior I can't control. The user-level actions that trigger the
problem are
This is a good description, but it's still abstract. Can you post a
simplified test-case project which reproduces the issue?
- I have used ObjectAlloc to debug this, and it confirms that the
first document's managedObjectContext remains allocated after its
"host" document has been released.
There are many reasons this could happen, and not all of them are
wrong, but again it's much harder to nail this down without a sample
project.
- Scott
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
