Re: Core Data grinds for 30 min saving SQLite. 10.6 Bug?
Re: Core Data grinds for 30 min saving SQLite. 10.6 Bug?
- Subject: Re: Core Data grinds for 30 min saving SQLite. 10.6 Bug?
- From: Nick Zitzmann <email@hidden>
- Date: Mon, 15 Apr 2013 15:20:39 -0600
On Apr 15, 2013, at 2:22 PM, Jerry Krinock <email@hidden> wrote:
>> Yes. I haven't checked to see if this was addressed in later cats, but I did notice that CoreData is a memory hog in Snow Leopard. Specifically, it allocates up to twice the size of the managed object when updating or deleting (!) the object, so if you have an object that is a few hundred megabytes in size and the process is running in 32-bit mode, then it may not be able to update/delete the object.
>
> Thank you, Nick. These are some interesting clues. But there must be something else going on in this case, because this store contains only several dozen small objects. The size of the .sql file, before and after saving, is only 112 KB.
Okay, that's pretty bizarre and I haven't seen that happen before. I don't suppose your user could use Instruments' object allocation instrument to figure out what's going on…? That would require installing Xcode from the App Store.
Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
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