-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Connection leak #1717
Comments
Thanks, I'll try out the repro locally. Do you have any more details that would help me while I look? Is it consistently leaking the connection immediately, or only occassionally? |
It's consistently leaking with payloads of 1 MB. I have only tried and reproduced in on Linux. |
I have just added a negative example with src/bin/worker-non-stream.rs - if we .concat2() the body (i.e. not stream it back) there is no leak. |
Is the leak in broker, or in worker? |
The connection between the worker and the broker is not closed from both sides - verified with lsof. |
I see, it seems the dispatcher after having written the headers for some reason doesn't continue to do work, but stalls. I'll look more into it. |
I've published v0.12.16 with a fix for this, thanks for reporting and for the reproducible instructions! |
Hyper-0.12.16 resolves hyperium/hyper#1717
In certain cases I see connection leaks. I have a simple reproduction in: https://github.com/luben/repro-hyper
The behavior I observe:
The text was updated successfully, but these errors were encountered: