-
-
Notifications
You must be signed in to change notification settings - Fork 232
Segfault when exiting classic server with running sweep thread [CORE5641] #5907
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
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Modified by: @AlexPeshkoffreporter: Alexander Peshkov [ alexpeshkoff ] => Pavel Zotov [ tabloid ] |
Modified by: @AlexPeshkoff |
Modified by: @AlexPeshkoff |
Modified by: @AlexPeshkoff |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5.8 [ 10809 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Cannot be tested |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @AlexPeshkoffdescription: Degfault happens if sweep thread does not get enough CPU resources to complete in a case of exit from classic server instance. => Segfault happens if sweep thread does not get enough CPU resources to complete in a case of exit from classic server instance. |
Submitted by: @pavel-zotov
Relate to CORE5429
Segfault happens if sweep thread does not get enough CPU resources to complete in a case of exit from classic server instance.
Commits: b183489
The text was updated successfully, but these errors were encountered: