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

[BUG] Getting "websocket: internal error, unexpected bytes at end of flate stream" despite protecting write calls with mutex #858

Open
1 task done
NeonWizard opened this issue Oct 20, 2023 · 0 comments
Labels

Comments

@NeonWizard
Copy link

NeonWizard commented Oct 20, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

I've been getting "websocket: internal error, unexpected bytes at end of flate stream" followed by the socket becoming unwriteable. From looking at the other issue in this repo, it looks like this might happen when simultaneously writing to the same connection. However, in my application I've protected Write calls with a mutex. What other scenarios can cause this? Are there race conditions in the library, such as with WriteControl?

Expected Behavior

Should not be getting these errors.

Steps To Reproduce

It happens rarely, it's not able to be consistently reproduced.

Anything else?

No response

@NeonWizard NeonWizard added the bug label Oct 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

1 participant