Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix geth transaction tracer #6652

Merged
merged 1 commit into from
Feb 8, 2023
Merged

Fix geth transaction tracer #6652

merged 1 commit into from
Feb 8, 2023

Conversation

Qwerty5Uiop
Copy link
Collaborator

Resolves #6638

Motivation

There is a similar issue and its solution in go-ethereum repo which are not yet included in any release, so we can apply this fix on our side for now.

Changelog

If the tracer tries to access memory beyond the available limit, we limit it to the end of the memory.

rude69

This comment was marked as spam.

rude69

This comment was marked as spam.

rude69

This comment was marked as spam.

@feld
Copy link

feld commented Jan 6, 2023

Blockscout with this change: tracer errors still happen

Blockscout with this change and geth with this fix: tracer errors still happen

Blockscout unchanged and geth with this fix: different errors -- application=indexer fetcher=internal_transaction count=10 error_count=10 [error] failed to fetch internal transactions for blocks: :closed

@vbaranov vbaranov merged commit 2c40a51 into master Feb 8, 2023
@vbaranov vbaranov deleted the fix-js-tracer branch February 8, 2023 11:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Goerli: geth internal transactions fetching with tracer.js causes "tracer accessed out of bound memory"
4 participants