-
Notifications
You must be signed in to change notification settings - Fork 594
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
HTTP/2: MemoryLeak in AlpnSwitcher #886
Comments
Taking a stab at it |
ktoso
added a commit
to ktoso/akka-http
that referenced
this issue
May 1, 2017
This technically is very similar to CoupledTerminationFlow, however since it's "sub" sources/sinks we could not directly use that.
ktoso
added a commit
to ktoso/akka-http
that referenced
this issue
May 1, 2017
This technically is very similar to CoupledTerminationFlow, however since it's "sub" sources/sinks we could not directly use that.
ktoso
added a commit
to ktoso/akka-http
that referenced
this issue
May 2, 2017
This technically is very similar to CoupledTerminationFlow, however since it's "sub" sources/sinks we could not directly use that.
ktoso
added a commit
that referenced
this issue
May 2, 2017
This technically is very similar to CoupledTerminationFlow, however since it's "sub" sources/sinks we could not directly use that.
tomrf1
pushed a commit
to tomrf1/akka-http
that referenced
this issue
Aug 13, 2017
This technically is very similar to CoupledTerminationFlow, however since it's "sub" sources/sinks we could not directly use that.
tomrf1
pushed a commit
to tomrf1/akka-http
that referenced
this issue
Aug 13, 2017
Follow up from akka#886's PR
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
AlpnSwitcher currently doesn't propagate connection closure to inner substreams. This leads to the implementation staying alive after the connection has been closed.
The text was updated successfully, but these errors were encountered: