-
Notifications
You must be signed in to change notification settings - Fork 20.5k
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
Maybe a deadlock in p2p? #703
Comments
Could you please point me to the code that is causing this? From the trace, it looks like there are multiple servers, one that is currently stopping and one that's still live. |
This is caused with my existing tests, I haven't yet rewritten them to use |
Trying them now. |
Your branch is based on an old-ish (last week) commit. I fixed this issue in f1d710a. |
Not really, even though that particular branch did indeed not contain your fix, if I merge the current develop branch with my test is still hangs. I'll try and prepare a clean repro branch. |
Could you please verify this branch? https://github.com/karalabe/go-ethereum/tree/p2p-hang-repro I am experiencing the same lockup and as far as I see here all the fixes are already included. |
I am seeing a hang on this waitgroup: https://github.com/ethereum/go-ethereum/blob/develop/p2p/peer.go#L145 Specifically, the |
Yes, seeing it. |
Found it. Will submit a fix later today. |
Great :) I'm off for today, but will check it out in the morning. |
Please retry when #704 is merged. Your test no longer hangs on my machine after merging this PR locally. |
…-unit-tests Make sure unit tests passed on tomoX branch
* docker: adds sleep 1 before running geth * scripts: docker should now exit using CTRL+c
Hey all,
I'm running some custom whisper tests on develop, and one of my tests always hangs when shutting down a few P2P server instances. I am Start()-ing two p2p.Server-s, wiring them together with SuggestPeer(), and Stop()-ing them afterwards. The first successfully terminates, but the second stop hangs. Am I doing something that I shouldn't be, or is this really a bug?
Here's a forced dump if someone with a bit more experience can spot an issue (note, the first goroutine in the below list is just the forced panic):
The text was updated successfully, but these errors were encountered: