On Apr 15, 2013, at 2:22 PM, Jerry Krinock <[email protected]> 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 protected])

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 [email protected]

Reply via email to