On 2013 Jan 23, at 23:07, Quincey Morris quinceymor...@rivergatesoftware.com
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
I received a crash report from a user indicating EXC_BAD_ACCESS in
-[NSConditionLock unlockWithCondition:]. Since the 'condition' parameter is an
integer, I think the only explanation is that the receiver must have been
deallocced. That didn't seem possible at the time when
On Jan 23, 2013, at 22:38 , Jerry Krinock je...@ieee.org wrote:
My theory is that, on these rare occasions, the thread running
-unlockWithCondition: would run enough to unblock the other thread, and,
oddly but legally, the system would then pause this thread before this method
had
