Currently, if any Client thread is blocked in a call to waitForConditionOrInterrupt, it will show up in the currentOp output as both "active:true" and with a "waitingForLatch" field identifying the Mutex associated with the condition variable being waited on. This output suggests the Mutex (Latch?) is locked and that the code is blocked waiting to acquire it, but this is a false suggestion.