execution/state: stack overflow on a withdrawn destruct on #26247's branch, fixed on main

Open
#26,359 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@sudeepdino008 is already working on this.

Since Nov 15, 2026.

Assessment

This issue has not been assessed yet.

Description

#26247's head 8e58488ae3 crashed the BSC mainnet archive node in parallel execution.

  • fatal error: stack overflow in the batch after block 17,832,509
  • cycle: versionedAccountBase → eip8246PreservedAccount → readBalance → versionedReadCore → getStateObject, entered from Exist on a CALL
  • trigger: a destruct the tx memoized is withdrawn; the reconstruction runs for any destruct, not only under EIP-8246

Main is fixed by #25491 (6ac9c93bbeb); the branch merges main only up to 46d3804b1e.

tree withdrawn-destruct test
main c6b74e97fc0 PASS
8e58488ae3 stack overflow

Fix: merge main into the branch. The node runs on an unpushed local commit with the same guard since 14:19Z.

Dominant language
Go
Stars
3.6k
Forks
1.6k
Avg merge
1d 17h
Merged PRs (30d)
820

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from erigontech/erigon

All issues in erigontech/erigon

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.