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
Lock manager code may create 100% CPU load for some time [CORE1985] #2423
Comments
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
Modified by: @hvladFix Version: 2.5 Beta 1 [ 10251 ] Fix Version: 2.1.2 [ 10270 ] Fix Version: 2.0.5 [ 10222 ] |
Commented by: @hvlad The issue is a regression introduced in v2.5 |
Modified by: @hvladVersion: 2.5 Alpha 1 [ 10224 ] Version: 2.0.4 [ 10211 ] => Version: 2.1.0 [ 10041 ] => Version: 2.5 Initial [ 10260 ] => Version: 1.5.5 [ 10220 ] => Version: 2.0.3 [ 10200 ] => Version: 2.0.2 [ 10130 ] => Version: 2.0.1 [ 10090 ] => Version: 1.5.4 [ 10100 ] => Version: 2.0.0 [ 10091 ] => Version: 1.0.3 [ 10006 ] => Fix Version: 2.1.2 [ 10270 ] => Fix Version: 2.0.5 [ 10222 ] => |
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
Process waiting for lock in wait_for_request() may loop instead of waiting for event after remapping of shared memory until real event occured
Commits: 40f3722
The text was updated successfully, but these errors were encountered: