Fast mutex could be left in locked state by dead process [CORE3326] #3692
Submitted by: @hvlad
If some process acquire fast mutex and died not releasing it it could hung all other activity.
Fast mutex was contributed by Yaffil team and integrated into Firebird 2.1. Since that time there was no reports about issues related to fast mutex robustness.
The text was updated successfully, but these errors were encountered: