small medium large xlarge

Back to: All Forums  Core Data
Wedding photobooth_pragsmall
18 Jan 2010, 23:32
Tony Arnold (11 posts)

Is this error really as straight forward as it looks? It’s happening on a user’s machine, so I don’t have direct access to check what is causing this. Could it be a simple case of file locking at the app or OS level?

Bizarre - it’s a new one for me.

Avatarsmall_pragsmall
19 Jan 2010, 00:35
Marcus S. Zarra (284 posts)

A new one to me as well. Could be a locked file or an issue with their hard drive. I would suggest that you have the user run disk utility to eliminate that possibility.

Wedding photobooth_pragsmall
21 Jan 2010, 21:10
Tony Arnold (11 posts)

Thanks Marcus, will do. The only other thing I can think of is that I’m overloading with saves somehow - I call save: on my managed object context on a 3 second delay each time NSManagedObjectContextObjectsDidChangeNotification fires (although in theory that’s not happening a lot).

Wedding photobooth_pragsmall
21 Jan 2010, 21:15
Tony Arnold (11 posts)

Just ran the Instruments Core Data tools over my app - nothing of note. It’s actually wonderfully efficient (thanks to your book!).

I’ll ask the users to run disk utility and see if there’s anything unusual going on.

You must be logged in to comment