Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Deadlock while syncing + JSONRPC #1058

Closed
gavofyork opened this issue May 8, 2016 · 2 comments
Closed

Deadlock while syncing + JSONRPC #1058

gavofyork opened this issue May 8, 2016 · 2 comments
Labels
F2-bug 🐞 The client fails to follow expected behavior.

Comments

@gavofyork
Copy link
Contributor

syncing hanged when serving jsonrpc call while syncing

[ #869387 9757…4099 ]---[ 28 blk/s | 167 tx/s | 40392121 gas/s  //··· 0/4 peers, #899522, 0+30125 queued ···// mem: 0 bytes db, 126 KiB chain, 23 MiB queue, 302 KiB sync ]
[ #869387 9757…4099 ]---[ 0 blk/s | 0 tx/s | 0 gas/s  //··· 0/4 peers, #899522, 0+30125 queued ···// mem: 0 bytes db, 126 KiB chain, 23 MiB queue, 302 KiB sync ]
[ #869387 9757…4099 ]---[ 0 blk/s | 0 tx/s | 0 gas/s  //··· 0/5 peers, #899522, 0+30125 queued ···// mem: 0 bytes db, 126 KiB chain, 23 MiB queue, 302 KiB sync ]
[ #869387 9757…4099 ]---[ 0 blk/s | 0 tx/s | 0 gas/s  //··· 0/5 peers, #899522, 0+30125 queued ···// mem: 0 bytes db, 126 KiB chain, 23 MiB queue, 302 KiB sync ]
...

was running web3.eth.getBlock, web3.eth.getUncleCountByBlockNumber, web3.eth.getUncleByBlockNumberAndIndex while syncing.

@gavofyork gavofyork added the F2-bug 🐞 The client fails to follow expected behavior. label May 8, 2016
@sammy007
Copy link

sammy007 commented May 9, 2016

While syncing several times from scratch I noticed same behaviour when not using jsonrpc.

@gavofyork
Copy link
Contributor Author

possibly fixed by #1095

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F2-bug 🐞 The client fails to follow expected behavior.
Projects
None yet
Development

No branches or pull requests

2 participants