We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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?
to your account
Submitted by: @hvlad
lock.cpp\post_blockage() could enter endless loop if, while delivering in-process AST, next blocking request will be freed by its owner.
It was reproduced when testing nbackup. I see no chance to this bug to occur in ClassicServer because it not released LM's mutex
in signal_owner() rountine so blocking requests queue is stable.
While i didn't tested v2.0.x i believe its affected too.
v2.5 is not affected as it already have similar fix made during refactoring LM internals.
The text was updated successfully, but these errors were encountered:
assignee: Vlad Khorsun [ hvlad ]
Sorry, something went wrong.
status: Open [ 1 ] => Resolved [ 5 ]
resolution: Fixed [ 1 ]
Fix Version: 2.1.4 [ 10361 ]
summary: 100% CPU load => 100% CPU load (endless loop) inside the lock manager
status: Resolved [ 5 ] => Closed [ 6 ]
status: Closed [ 6 ] => Closed [ 6 ]
QA Status: Cannot be tested
No branches or pull requests