Re: Two kinds of NSManagedObject fault?
Re: Two kinds of NSManagedObject fault?
- Subject: Re: Two kinds of NSManagedObject fault?
- From: Frédéric Testuz <email@hidden>
- Date: Sat, 08 Mar 2014 20:45:20 +0100
Le 8 mars 2014 à 03:54, Jerry Krinock <email@hidden> a écrit :
> Sixten is correct about -isDeleted. It is rarely useful.
>
> Regarding these two kinds of managed object faults, your “second” kind is similar to what I described in a message I posted earlier today [1]. In my case,
>
> -isFault returns NO
> -isDeleted returns NO
> -retainCount returns +1 or greater
> -get<aNumberAttribute> works OK
> -get<aStringAttribute> works OK
> -get<aDateAttribute> makes EXC_BAD_ACCESS
> -get<aRelationship> makes EXC_BAD_ACCESS
> -set<anyProperty> makes EXC_BAD_ACCESS
>
> I don’t know what to make of this either. I was wondering if maybe the object’s managed object context had been reset.
I suspect that in your test case, the number are tagged pointers, then they are never deallocated as they are not allocated in first place. And are you sure that the string tested are not static strings (NSCFConstantString) ? These ones are also never deallocated.
Frédéric
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden