Fix leaking timer goroutines #186
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thanodnl
reviewed
Nov 10, 2016
| ticker.Stop() | ||
| } | ||
| close(rp.tickersStop) | ||
| rp.tickersStop = nil |
Contributor
There was a problem hiding this comment.
This line causes a data race with lines 229 and 247. Is it really needed to set it to nil when the timers are stopped?
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes two leaking goroutines from the ringpop timers. There is still one more leaking goroutine that I'm aware of in rcrowley/go-metrics:
https://github.com/rcrowley/go-metrics/blob/master/meter.go#L218-L225
That's a ticker that would also require a stop channel.