I have an app which writes a log to a Core Data SQLite store. I just got a Logs.sql file from a user. It is 270 KB, containing 1251 log entries. Upon launch, the app finds that 284 entries are expired and deletes them. Nothing out of the ordinary so far.
App then executes -[NSManagedObjectContext save:]. This method thrashes for 30 minutes, with memory usage increasing slowly, until system won't give any more and then it crashes. Is there any programming error by which I could make a Core Data store unsaveable like this? I don't think so. Probably I should report this as a bug if it does it in Lion. More generally, can anyone suggest how to recover when an Apple method won't return on the main thread? If it was on a secondary thread, I could kill it with a timeout (leaks, I know), but anyhow I've never considered myself smart enough to do Core Data on secondary threads. Usually this little task takes a few milliseconds, and I slip it in during idle time. Jerry Krinock _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
