Issue: reth-optimism-node::it p2p_version::peers_negotiate_eth_69 intermittently exits with SIGSEGV after the test body reports ok.
Date: 2026-05-22
The original findings are directionally correct: upstream reth changed the payload builder from a Tokio task to an untracked OS thread, and op-reth inherits that path. I could not reproduce the exact SIGSEGV locally, including on native x86_64 Ubuntu inside Docker, but I did reproduce the lifecycle hazard directly by patching reth to widen the race window. The patched run shows orphan payload-builder OS threads touching a Tokio runtime after shutdown has begun.