You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The client uses WithContext to create a context for signaling shutdown to sub go-routines. This seems to make the context leak when the workers return without cancelling the context. The cancel function must be run always.
It seams the context that is generated on 'Start' is leaked at least if the Dial fails. The workaround is to call Stop always. There or other contexts that are generated via WithCancel, that look suspiciously like leaks, but I didn't check if that is the case.
The text was updated successfully, but these errors were encountered:
The client uses WithContext to create a context for signaling shutdown to sub go-routines. This seems to make the context leak when the workers return without cancelling the context. The cancel function must be run always.
It seams the context that is generated on 'Start' is leaked at least if the Dial fails. The workaround is to call Stop always. There or other contexts that are generated via WithCancel, that look suspiciously like leaks, but I didn't check if that is the case.
The text was updated successfully, but these errors were encountered: