Fix potential indefinite stalling of chainstate and mempool if the initial sync is run on a slow machine with lots of peers#2007
Merged
ImplOfAnImpl merged 3 commits intomasterfrom Feb 6, 2026
Conversation
…te stalling of the node during initial sync
OBorce
approved these changes
Feb 6, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I described the details in
ml-node-consensusin Slack.Basically, the stalling was due to how
block_in_placeinteracts with deferred wakers in tokio; this behavior has been reported here and it has been fixed since then. So the fix for the stalling is to upgrade tokio to a version that includes that fix.Additionally, I updated the "bytes" and "oneshot" crates to fix vulnerabilities reported by
cargo denyand rancargo vet prune.