• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Weird (fatal) CoreData caching behavior
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Weird (fatal) CoreData caching behavior


  • Subject: Re: Weird (fatal) CoreData caching behavior
  • From: Scott Stevenson <email@hidden>
  • Date: Tue, 20 Mar 2007 20:00:00 -0700


On Mar 20, 2007, at 7:41 PM, Doug Knowles wrote:

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

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Weird (fatal) CoreData caching behavior (From: "Doug Knowles" <email@hidden>)

  • Prev by Date: Re: DVD as desktop
  • Next by Date: Embedding a WebView in a Table
  • Previous by thread: Weird (fatal) CoreData caching behavior
  • Next by thread: Embedding a WebView in a Table
  • Index(es):
    • Date
    • Thread