Skip to content
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

possible concurrency bug causing lockup #118

Open
paralin opened this issue Oct 26, 2022 · 2 comments
Open

possible concurrency bug causing lockup #118

paralin opened this issue Oct 26, 2022 · 2 comments
Labels
P3 Low: Not priority right now

Comments

@paralin
Copy link
Contributor

paralin commented Oct 26, 2022

Maybe related to #115

Had an issue developing starpc where sometimes (~10% of the time) the test would get stuck on recv() on both ends even after one side had sent the packet it was waiting for.

I was not able to figure out where the actual issue is located, but after I switched out mplex for yamux, the issue is gone.

So, I think the lockup issue must be in mplex somewhere.

@marten-seemann
Copy link
Contributor

Is there any reason you're using mplex instead of yamux?

@paralin
Copy link
Contributor Author

paralin commented Oct 27, 2022

Not using mplex anymore - switched to yamux. Just reporting the issue on mplex

@p-shahi p-shahi added this to go-libp2p Nov 7, 2022
@p-shahi p-shahi added this to the Best Effort Track milestone Nov 7, 2022
@p-shahi p-shahi added the P3 Low: Not priority right now label Nov 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 Low: Not priority right now
Projects
Status: No status
Development

No branches or pull requests

3 participants