mutex-lock! leaves mutex in wrong state
|Reported by:||joergw||Owned by:|
If (and only if) a thread calling (mutex-lock! <muxtex> #f #f) had to wait for it the mutex state is left to be owned by the calling thread instead of 'not-owned.