opt: fix the potential goroutine leak after calling Release()
#287
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.
…rom Release method
name: Refactor Release Methods
about: Call cleanup functions when Release() is called.
title: ''
labels: ''
assignees: ''
1. Are you opening this pull request for bug-fixs, optimizations or new feature?
Bug fix.
2. Please describe how these code changes achieve your intention.
By moving stopTicktock and stopPurge into Release() methods from ReleaseTimeout(), these functions will be stopped when Release() is called.
3. Please link to the relevant issues (if any).
#244
4. Which documentation changes (if any) need to be made/updated because of this PR?
4. Checklist