You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Geth version: 1.13.11, 1.13.15, 1.14.0
OS & Version: OSX
Expected behaviour
In dev mode, when the client sends transactions from two different addresses, it could be mined.
Actual behaviour
After version 1.13.11 if I send two transactions from two different addresses concurrently, the miner deadlock on txpool sync, and could not produce new blocks.
The simulated beacon API hang in the api.eth.TxPool().Sync()at this line. In the Sync(), it will trigger more new transaction events and the subscriber could not handle it, so it deadlocked. If I changed the chan size in eth/catalyst/simulated_beacon_api.go, it could allow more concurrent transactions.
System information
Geth version:
1.13.11
,1.13.15
,1.14.0
OS & Version: OSX
Expected behaviour
In dev mode, when the client sends transactions from two different addresses, it could be mined.
Actual behaviour
After version
1.13.11
if I send two transactions from two different addresses concurrently, the miner deadlock on txpool sync, and could not produce new blocks.The simulated beacon API hang in the
api.eth.TxPool().Sync()
at this line. In theSync()
, it will trigger more new transaction events and the subscriber could not handle it, so it deadlocked. If I changed the chan size ineth/catalyst/simulated_beacon_api.go
, it could allow more concurrent transactions.Steps to reproduce the behaviour
geth command to start in the dev mode
And the client is written by ethers.js
The text was updated successfully, but these errors were encountered: