-
Notifications
You must be signed in to change notification settings - Fork 164
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
How to debug snappy: corrupt input? #73
Comments
I think we figure out the reason now: How to reproduce the issue:
So the snappy can always report the error Misleading error message
|
I got this error because the net.Conn being read multiple times concurrently |
Hi team, we met an error
snappy: corrupt input
while using snappy to compress through a TCP connection.How we build the connection:
On the source side:
On the destination side:
We get the error
snappy: corrupt input
whenconn.Read(buf)
. And this error happens intermittently.Is this caused by network problem?
We read some snappy code, and we know that this error is reported because the checksum or the decode result length is wrong. But we use snappy based on a TCP connection and TCP can guarantee data integrity. So if snappy needs several network packages to decode the complete data? Or this is caused by some problem with the network card, the hardware cannot verify the data correctly.
Is this caused by memory problem?
I also find some discussions on the network that suspect this is caused by memory overflow or runtime memory limit not enough. But I cannot make sure. Since we don't get any other error messages.
I'd appreciate any help or suggestions on how to debug. Thanks!
The text was updated successfully, but these errors were encountered: