[3646] Fix a shutdown problem in block_processor #44
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ootstrap block count
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
2022-01-04T15:26:36Z cryptocode
My node crashed occasionally during shutdown with an invalid mutex termination in the block_processor destructor.
The issue is that processing threads are running while the node is tearing down, leading to UB.
occurs in the destructor rather than , at which point most of the node instance is gone.
The destructor seemed wrong anyway as it calls stop, which the node also calls. The proposed solution is to move the destructor's joining of processing_thread to and remove the destructor.