Repository navigation
Conversation
Picks up paradigmxyz/revm-inspectors#487, which makes the default struct logger honor the `limit` option and stop recording steps once it is hit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Author
|
Closing: optimism#24024 moves the monorepo to the |
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
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.
Lets RPC callers cap the memory a
debug_traceCallordebug_traceTransactionuses with the default tracer.On revm-inspectors 0.43, the default struct logger ignores the
limitoption. It records every opcode step, so a high-gas call can grow a node's memory to tens of GiB and get it OOM-killed. paradigmxyz/revm-inspectors#487, first released in 0.44.0, stops recording oncelimitsteps are captured. This bumps to 0.44.3, the latest patch release.Worth reviewing:
limitdoes not stop the default tracer from copying contract storage on everySLOAD/SSTORE. That is still on upstream main, so storage-heavy calls inside the limit can still use a lot of memory.Not verified:
reth-rpc,reth-rpc-eth-apiandreth-rpc-eth-typeswere checked locally. Clippy is clean and their tests pass, but the full workspace was not built.🤖 Generated with Claude Code