On Thu, Oct 30, 2008 at 5:30 PM, Michael Ash <[EMAIL PROTECTED]> wrote: > Based on the state of the program when it crashes, it appears that the > problem is caused by a race condition which occasionally causes two of > the worker threads that NSOperationQueue spawns to dequeue and execute > the same NSOperation. Since an NSOperation is only supposed to run > once, things fall down go boom. This is just a theory, mind, and I'm > not sure of it yet.
I'm not sure it would help, but it might. You could try using the dependency mechanism in addition to setting maxConcurrentOperations to 1. Keep track of the last NSOperation in your for loop and assign in as you go. If that fixes it, it could be a race in maxConcurrentOperations. This is all highly speculative. -Colin _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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]
