-
Notifications
You must be signed in to change notification settings - Fork 879
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
Backport fix to 17.03 #1784
Backport fix to 17.03 #1784
Conversation
Stacktrace related to 17.03:
Stacktrace related in 17.03:
|
Not ready yet, looks like there is still something missing to handle the stacktrace reported above |
I'm confused - is the problem with the backport, or is the stack trace in #1784 (comment) unrelated to what was fixed here? |
@aaronlehmann sorry for the confusion, but I will group here all the backports for all the fixes for the goroutine leaks.
|
Wait for the master one to be reviewed and accepted: |
Fixed cancelling method call to avoid go routine leaks Signed-off-by: Flavio Crisciani <flavio.crisciani@docker.com>
The channel ch.C is never closed. Added the listen of the ch.Done() to guarantee that the goroutine is exiting once the event channel is closed Signed-off-by: Flavio Crisciani <flavio.crisciani@docker.com>
On linux systems bump up gc_thresholds so to lower the probability of running with neighbor table overflow issues Signed-off-by: Flavio Crisciani <flavio.crisciani@docker.com>
The netlink socket that was used to monitor the L2 miss was never being closed. The watchMiss goroutine spawned was never returning. This was causing goroutine leak in case of createNetwork/destroyNetwork Signed-off-by: Flavio Crisciani <flavio.crisciani@docker.com>
The feature was not getting properly triggered, move it as first operation in the configure Signed-off-by: Flavio Crisciani <flavio.crisciani@docker.com>
LGTM |
Fixed cancelling method call to avoid go routine leaks
Signed-off-by: Flavio Crisciani flavio.crisciani@docker.com