-
Notifications
You must be signed in to change notification settings - Fork 41
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
goroutine leak in Context.Run? #29
Comments
Do you think #23 would resolve it? |
No - the goroutine will still stay around until the |
Hmmm I think that makes sense - @progrium thoughts? - and would take a PR :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems there is a goroutine leak in Context.Run: https://github.com/progrium/go-basher/blob/master/basher.go#L267 goroutine is launched which iterates over signals chan. But the chan is never closed, so the routine never exits... shouldn't there be something like
after
signal.Notify(signals)
call?The text was updated successfully, but these errors were encountered: