Wait a minute, Jonathan, would it be sufficient to simply
lock the mutex before trying to destroy it? Or am I missing
something here?
If the problem exists in 3.3+ad13, I at least have never encountered
it there, despite fairly heavy use of ns_mutex from multiple threads.
But perhaps I coincidentally happen to not be triggering the bug.
