Fixing a potential memory leak problem #41
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.
The underlying Timer is not recovered by the garbage collector until the timer fires. It's better to use time.NewTimer instead and call its Stop method when the timer is no longer needed to avoid potential memory leak issues.
It's hard to run into a memory leak issue in 5 seconds, but it will potentially reduce memory pressure when there are many short-lived subscribers.