On Dec 15, 2009, at 8:05 PM, PCWiz wrote: > *** -[NSRecursiveLock unlock]: lock (<NSRecursiveLock: 0x16c2340> '(null)') > unlocked from thread which did not lock it > *** Break on _NSLockError() to debug. > *** -[NSRecursiveLock finalize]: lock (<NSRecursiveLock: 0x16ca9c0> '(null)') > finalized while still in use > *** Break on _NSLockError() to debug. > > I've gotten these before, and they don't seem to affect the operation of the > app so I doubt this is what's causing my problem
They're almost certain to cause other problems though, probably in an intermittent and difficult-to-reproduce way. This is a sign that something is seriously wrong with the way you're using locks. See my previous post ... locks are like guns, you definitely don't want to mess around with them without having been trained in how to use them safely. —Jens_______________________________________________ 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 arch...@mail-archive.com
