Skip to content
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

100% CPU load (endless loop) inside the lock manager [CORE3285] #3653

Closed
firebird-issue-importer opened this issue Dec 21, 2010 · 5 comments
Closed

Comments

@firebird-issue-importer

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.

Commits: af3222f

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 21, 2010

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 21, 2010

Modified by: @hvlad

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.1.4 [ 10361 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 21, 2010

Modified by: @dyemanov

summary: 100% CPU load => 100% CPU load (endless loop) inside the lock manager

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Feb 4, 2011

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jul 16, 2015

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: Cannot be tested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants