-
Notifications
You must be signed in to change notification settings - Fork 20
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
PANIC in readNext #43
Comments
Secio could be returning the wrong length. That's all I can think of. |
I've found libp2p/go-msgio#12 but I don't think that's the cause. |
I have encountered this panic problem too and it's hard to reproduce. I look forward to your progress. |
Another one crashed; so it's a real bug, not some cosmic ray.
|
I can confirm that the bug is still there, another one crashed running with the msgio patch. |
Progress: Running with with the patch in #45 triggers the oversize read assertion:
|
So the underlying connection claims to have read more than what space is available in the buffer. |
Pull in a panic fix and a fix for libp2p/go-mplex#43
We have high hopes for libp2p/go-libp2p-secio#44 fixing the issue; we'll just have to wait a few days and see if any more crashes are observed in the relays. |
A relay has crashed with an index out of range.
The text was updated successfully, but these errors were encountered: