-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
Websocket stuck after receiving around ~16 kb of data from client #80
Comments
Which version are you using? We fixed this in #78. |
@mcollina latest one, 2.0.9 |
I checked that pure ws@7.3.1 with default settings works stably (without calling connection.resume()):
|
4 tasks
mcollina
pushed a commit
that referenced
this issue
Oct 8, 2020
* fix: Resume connection stream before continuing. [#80] * chore: Remove redundant listener. * chore: Linted code
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐛 Bug Report
After client sends ~100 messages of ~160 bytes each to websocket,
connection.socket.on('message')
is no longer being triggered.It seems to be size-dependent, I can send thousands of very short (a few bytes) messages, but only around 100 lines of 160 bytes.
To Reproduce
In new dir:
Create
server.js
:Run
node server.js
In another window, run:
Create a file with ~150 lines of 160 bytes each. Copy-paste contents into wscat.
The server will stop responding.
Expected behavior
Should keep returning responses.
Your Environment
The text was updated successfully, but these errors were encountered: