New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fast mutex could be left in locked state by dead process [CORE3326] #3692
Comments
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5.1 [ 10333 ] Fix Version: 3.0 Alpha 1 [ 10331 ] |
Commented by: @samofatov Well, the hanging happened quite regularly if you have 100's of users on a faulty network. CORE3153 is the earlier incarnation of this bug |
Commented by: @hvlad So far, you are the only one who reported such issue. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Cannot be tested |
Submitted by: @hvlad
Replaces CORE3153
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.
I reproduced hung in very specific scenario and only as result of another bug (see CORE3325).
Commits: a98fb23 1b96d77 8fa4349 4d0a3d3
The text was updated successfully, but these errors were encountered: