• 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: Cococa-Dev : was [coredata count not fulfill fault after object delete]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cococa-Dev : was [coredata count not fulfill fault after object delete]


  • Subject: Re: Cococa-Dev : was [coredata count not fulfill fault after object delete]
  • From: Martin Hewitson <email@hidden>
  • Date: Mon, 14 Jan 2013 09:42:33 +0100

On Jan 13, 2013, at 9:32 PM, Jerry Krinock <email@hidden> wrote:

>
> You've established previously that this is definitely a bug in Mac OS 10.6.

I'm not sure I had reached that decision. I have now been able to reproduce the problem with a bare-bones core data document app. But still I wonder if it is something to do with my model (which is now a fraction of the model from the original app). I notice on 10.8 that if I remove an object from the tree controller then I have to hit save twice to make the 'document dirty' spot disappear, hinting that there is something still wrong on 10.8, but it's swept under the carpet, whereas on 10.6.8 it isn't.


>  Your mission is to find a workaround.

Maybe - see above.

>
> On 2013 Jan 12, at 23:29, Martin Hewitson <email@hidden> wrote:
>
>> 2) Whenever I do [NSTreeController selectedObjects] I seem to end with an additional reference count. Is that expected?
>
> If you mean that there is an additional reference count long after the time when the object is no longer in use, which apparently prevents its deallocation, definitely not.  Furthermore, if you are saying that the excess reference count is proportional to the number of times that [NSTreeController selectedObjects] is invoked, maybe the bug in Mac OS 10.6 is a memory leak in -[NSTreeController selectedObjects].  Try doing a Method Replacement on that method.  In your replacement implementation, invoke the original method, then invoke -autorelease.

Could you hint how to do that? A category on NSTreeController? Will -autorelease work with ARC?

>
> I'm not sure how this would cause a "Core Data could not fulfill a fault" exception, except that allowing dead managed objects to hang around is not a good thing.

That's a bit my problem too. Mixed metaphors not withstanding, I wonder if I'm just following a red herring down a dead end.

I'll keep digging at my bare bones test app to see if I can fix the issue. Maybe the next step is to drop back from an outlineview+treecontroller to a table+arraycontroller.

Thanks again for your  thoughts,

Martin

p.s. I could post the test app if anyone wishes to see it.



>
>
> _______________________________________________
>
> 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







_______________________________________________

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

  • Follow-Ups:
    • Re: Cococa-Dev : was [coredata count not fulfill fault after object delete]
      • From: Jerry Krinock <email@hidden>
References: 
 >Re: Cococa-Dev : was [coredata count not fulfill fault after object delete] (From: Martin Hewitson <email@hidden>)
 >Re: Cococa-Dev : was [coredata count not fulfill fault after object delete] (From: Mike Abdullah <email@hidden>)
 >Re: Cococa-Dev : was [coredata count not fulfill fault after object delete] (From: Martin Hewitson <email@hidden>)
 >Re: Cococa-Dev : was [coredata count not fulfill fault after object delete] (From: Mike Abdullah <email@hidden>)
 >Re: Cococa-Dev : was [coredata count not fulfill fault after object delete] (From: Martin Hewitson <email@hidden>)
 >Re: Cococa-Dev : was [coredata count not fulfill fault after object delete] (From: Martin Hewitson <email@hidden>)
 >Re: Cococa-Dev : was [coredata count not fulfill fault after object delete] (From: Peter <email@hidden>)
 >Re: Cococa-Dev : was [coredata count not fulfill fault after object delete] (From: Martin Hewitson <email@hidden>)
 >Re: Cococa-Dev : was [coredata count not fulfill fault after object delete] (From: Peter <email@hidden>)
 >Re: Cococa-Dev : was [coredata count not fulfill fault after object delete] (From: Martin Hewitson <email@hidden>)
 >Re: Cococa-Dev : was [coredata count not fulfill fault after object delete] (From: Martin Hewitson <email@hidden>)
 >Re: Cococa-Dev : was [coredata count not fulfill fault after object delete] (From: Jerry Krinock <email@hidden>)

  • Prev by Date: Re: Could somebody please fix NSTimer?
  • Next by Date: How to get registered dragged types from NSWindow?
  • Previous by thread: Re: Cococa-Dev : was [coredata count not fulfill fault after object delete]
  • Next by thread: Re: Cococa-Dev : was [coredata count not fulfill fault after object delete]
  • Index(es):
    • Date
    • Thread