Is it possible that the entity is retained but has been deleted from the MOC? I vaguely recall seeing this myself at one point in the dim past.
> On Mar 27, 2019, at 1:18 PM, Rick Mann <rm...@latencyzero.com> wrote: > > I can't tell. I don't believe I have any unreferenced MOCs. > >> On Mar 27, 2019, at 13:08 , Dave Fernandes <dave.fernan...@utoronto.ca> >> 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 <rm...@latencyzero.com> wrote: >>> >>> 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 of >>> async operation, so this entity gets created and destroyed often, making it >>> that much harder to figure out exactly what's going on. >>> >>> I can bulletproof the place where the crash occurs when the moc is nil, but >>> I'd really like to track down the underlying problem. >>> >>>> On Mar 27, 2019, at 12:17 , Mike Abdullah <mabdul...@karelia.com> wrote: >>>> >>>> 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 can also observe this affect on deleted objects >>>> once the context has been saved, if you’re still holding a reference to >>>> any such objects. >>>> >>>> Mike. >>>> >>>> Sent from my iPhone >>>> >>>>> On 26 Mar 2019, at 21:57, Rick Mann <rm...@latencyzero.com> wrote: >>>>> >>>>> The implication there is that an object has a weak reference to the MOC? >>>>> Ah, in the header I see it's `assign`. I wonder why they do that and not >>>>> `weak`. >>>>> >>>>> Thanks, I'll look into it. >>>>> >>>>>> On Mar 26, 2019, at 14:50 , Richard Charles <rcharles...@gmail.com> >>>>>> wrote: >>>>>> >>>>>> You have retained the managed object outside the managed object context. >>>>>> >>>>>> --Richard Charles >>>>>> >>>>>> >>>>>>> On Mar 26, 2019, at 1:04 PM, Rick Mann <rm...@latencyzero.com> wrote: >>>>>>> >>>>>>> I'm seeing a situation where my NSManagedObject's managedObjectContext >>>>>>> is nil. It doesn't happen all the time though. Any idea why? Thanks! _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
