Ledger Account Bloater - #79
Open
SeanCheatham wants to merge 2 commits into
Open
Conversation
SeanCheatham
force-pushed
the
seancheatham/payment-fund-new-shamap-repro
branch
2 times, most recently
from
July 22, 2026 00:20
cc0e4aa to
10eca25
Compare
SeanCheatham
force-pushed
the
seancheatham/payment-fund-new-shamap-repro
branch
from
July 22, 2026 00:48
10eca25 to
d020843
Compare
SeanCheatham
marked this pull request as ready for review
July 22, 2026 01:04
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
1 participant
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.
There's a somewhat mysterious condition which leads to a node crash. Logs leading up to this crash include many lines with
terminate called after throwing an instance of 'xrpl::SHAMapMissingNode'. This follows after network faults are injected which cause disruption to peer synchronization.In an attempt to surface this crash more frequently, this PR adds a new test driver which funds a random batch of new Accounts on the ledger. The intention is to bloat the ledger with new accounts, thus triggering more sync pressure.
This PR is not guaranteed to actually surface the issue; the hope is that it will though.