fix(invariant): prune calldata to bound memory usage in long runs #12893
+23
−40
Conversation
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
subwaycookiecrunch
requested review from
0xrusowsky,
DaniPopes,
grandizzy,
mattsse,
onbjerg and
zerosnacks
as code owners
DaniPopes
reviewed
Dec 21, 2025
Contributor
Author
There was a problem hiding this comment.
You're right , this file isn't required for the invariant memory fix.
Its presence here isn't intentional for this change, and I’ll remove it
from this PR so the scope stays minimal.
subwaycookiecrunch
force-pushed
the
fix/invariant-memory-usage
branch
from
278ae4d to
68b258a
Compare
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.
Description
Fixes #12397
This PR addresses the issue of unbounded memory usage during long-running invariant tests. Previously, the
InvariantExecutorretained the fullcalldatafor every successful fuzz case. In testing sessions with millions of runs (e.g., overnight fuzzing), this caused memory usage to grow indefinitely, eventually leading to OOM crashes.Changes
crates/evm/fuzz: Addedprune_calldata()methods toFuzzCaseandFuzzedCasesto allow clearing the stored calldata while preserving metrics (gas, stipend).crates/evm/evm: UpdatedInvariantExecutorto enforce a rolling window of stored calldata. It now keeps full traces only for the last 4,096 runs (for debugging purposes) and prunes the calldata from all older runs.Verification
calldatais pruned, the total count of runs and other metrics remain accurate for reporting.