-
Notifications
You must be signed in to change notification settings - Fork 48
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
openConnection and openConnectionSSL leak file descriptors on connect failures #44
Labels
Comments
ghost
assigned istathar
Nov 10, 2013
Finally have some time. Will be looking at this this week. |
Now I finally have some time. :/ Will be looking at this this week, and you can expect this addressed in 0.7.3 |
Any progress on this? |
I'm hammering on an IPv6 problem that may or may not be cause by this part of the code. Either way, I've hacking on http-streams this week. |
Maybe relevant to #105 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When attempting to open a connection to an address which can be successfully resolved but not connected to
openConnection
andopenConnectionSSL
leave the file descriptor belonging to the socket open.Test-case:
One has to handle exceptions within
openConnection*
to ensure the socket is closed, e.g.The text was updated successfully, but these errors were encountered: