-
Notifications
You must be signed in to change notification settings - Fork 20.3k
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
Untraceable transaction using debug_traceTransaction #23552
Comments
I am seeing this exact problem as well. Hey @MariusVanDerWijden - this is very similar to #23128. Currently using debug.standardTraceBlockToFile isn't an option because our processing of these transactions is synchronous / has to keep up with the blockchain. |
Another tx that we can't get to trace on our archive node is |
This seems to have occurred again for tx: |
Some transactions are too large to do over rpc:
In order to make this data smaller, one thing that can be done is to disable memory If the trace is hundreds of MB or even Gb, then this is bound to fail. For this specific reason, we implemented This method avoids the overhead, by sending traces immediately to a
This method is capable of tracing arbitrarily large transactions. Example to trace a specific transaction without memory:
This will write the trace-file to the |
Tracing the transaction with Tracing with
When executing with |
Disabling Memory and ReturnData in the RPC call lands me at 20 seconds
The trace for that is 122k |
our company has been able to trace every tx in ethereum history until this new batch which are around 23M gas in a single tx. it seems the new eip-1559 gas limit is allowing these mega transactions to bog down the tracer. we rely on tracing to show our customers their accurate transaction history and balance in real time |
Something else you can try is compressing the response, e.g. via
Update: maybe not the best idea. Tried it with https://etherscan.io/tx/0x1a7322e8ca73b4af0399b7d81d3830534e6ebdf2794fcbe4a4568028cd2f5d87 (23m usedGas) and geth went bOOM) |
Similar issue I am experiencing on the ETH Classic core-geth client. etclabscore/core-geth#412 |
#23558 This PR(disable the memory and returnData) should fix it. Close it now. |
System information
Geth version:
1.10.8
OS & Version: linux
Expected behaviour
The transaction
0x430874b252f837eecef4eefd51f94019d31b0cb2fa8cba78ebc98f33c660ade2
can't be traced by our archive node. I also tried on etherscan and their trace times out after 60s with a 'Raw traces operation timeout' error.I see on Etherscan that the tx cost over $6800 in gas fees, maybe that is related:
https://etherscan.io/tx/0x430874b252f837eecef4eefd51f94019d31b0cb2fa8cba78ebc98f33c660ade2
Steps to reproduce the behaviour
The text was updated successfully, but these errors were encountered: