-
Notifications
You must be signed in to change notification settings - Fork 312
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
Close should guarantee no more goroutines #330
Milestone
Comments
Nevermind, it shouldn't. The connection should always send a closure so the opposing end doesn't timeout on the connection. |
Nah this is an issue. I forgot to respond. Glad I remembered this lol. After Close() returns, you should be guaranteed that there are no more goroutines for the websocket. This is currently not the case. |
nhooyr
added a commit
that referenced
this issue
Oct 19, 2023
nhooyr
added a commit
that referenced
this issue
Oct 19, 2023
Fixed in dev. |
nhooyr
added a commit
that referenced
this issue
Oct 19, 2023
nhooyr
added a commit
that referenced
this issue
Oct 19, 2023
nhooyr
added a commit
that referenced
this issue
Oct 19, 2023
nhooyr
added a commit
that referenced
this issue
Oct 19, 2023
nhooyr
added a commit
that referenced
this issue
Oct 19, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If
Close
is called after the HTTP server has been closed, a goroutine currently leaks.The text was updated successfully, but these errors were encountered: