Re: Core Data SIGSEGV when opening an existing document
Re: Core Data SIGSEGV when opening an existing document
- Subject: Re: Core Data SIGSEGV when opening an existing document
- From: Larry Fransson <email@hidden>
- Date: Wed, 19 Apr 2006 03:32:10 -0700
On Apr 19, 2006, at 12:18 AM, mmalcolm crawford wrote:?
It's not clear why you're adding local pools? You typically use
local pools around loops etc. that *you* own. If you're
interrupting the "normal event cycle", it's quite possible you'll
end up releasing objects earlier than expected and *introduce*
errors (see in particular, for example, <http://developer.apple.com/
documentation/Cocoa/Conceptual/CoreData/Articles/cdMemory.html#//
apple_ref/doc/uid/TP40001860-DontLinkElementID_37>).
It was a desperate attempt to make the thing work. I understand now
the problems I could also be creating, which I hadn't realized
before. Thanks for that!
Why not start with something simple like explicitly fetching all
instances of all entities at startup (see "Batch Faulting..."
<http://developer.apple.com/documentation/Cocoa/Conceptual/CoreData/
Articles/cdPerformance.html#//apple_ref/doc/uid/TP40003468-SW3>)?
I had looked at it before, and I thought I tried to do something like
that, but it could be that I didn't quite get it right. I'll study
it some more. Thanks!
Larry Fransson
Subcritical
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden