I can't tell. I don't believe I have any unreferenced MOCs.
> On Mar 27, 2019, at 13:08 , Dave Fernandes wrote:
>
> Just to clarify, the moc exists, but the reference to it is nil? Or has the
> moc, itself, been deallocated?
>
>> On Mar 27, 2019, at 3:40 PM, Rick Mann wrote:
>>
>> This is pr
Just to clarify, the moc exists, but the reference to it is nil? Or has the
moc, itself, been deallocated?
> On Mar 27, 2019, at 3:40 PM, Rick Mann wrote:
>
> This is proving very hard to diagnose, as it doesn't always happen. I tried
> observing -managedObjectContext, but it never gets called
This is proving very hard to diagnose, as it doesn't always happen. I tried
observing -managedObjectContext, but it never gets called with a nil value.
Moreover, my entity's -dealloc method is sometimes called even though none of
the -awake methods gets called. This is a complex app with a lot o
Given the number of objects Core Data is designed to juggle, managing that
number of weak references might well affect performance. Besides, wouldn’t you
still the same result, that your object has a nil reference to the context
because the context has been deallocated?
Furthermore, I think you
