Re: Multithreading crash in -[NSConditionLock unlockWithCondition:]
Re: Multithreading crash in -[NSConditionLock unlockWithCondition:]
- Subject: Re: Multithreading crash in -[NSConditionLock unlockWithCondition:]
- From: Jerry Krinock <email@hidden>
- Date: Thu, 24 Jan 2013 06:51:38 -0800
On 2013 Jan 23, at 23:07, Quincey Morris <email@hidden> wrote:
> What's the source code line that invokes 'unlockWithCondition:'? If it's sending that message to a local variable, then the ARC version is safe
As it turns out, it was sending to a local variable, not due to any foresight on my part, but for convenience. Until yesterday when I read an old Mike Ash Friday Q&A on this topic, and now your explanation, I tended to use a local variable vs. repeating the accessor based on which required less typing or looked neater.
> this isn't a memory management issue, but rather a thread safety issue.
Yes, that's a good point.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden