Prevent timer leaks in Workerpool and others (#11333) #11340
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a potential memory leak in
Workerpool
due to the intricacies oftime.Timer
stopping.Whenever a
time.Timer
isStop
ped its channel must be cleared using aselect
if the result of theStop()
isfalse
.Unfortunately in
Workerpool
these were checked the wrong way round.However, there were a few other places that were not being checked.
Signed-off-by: Andrew Thornton art27@cantab.net
Co-authored-by: techknowlogick techknowlogick@gitea.io
Co-authored-by: Lunny Xiao xiaolunwen@gmail.com