fix: memory leak caused by timer that never quit #10614
Merged
+86
−75
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.
Description
The etcd related pr imported a timer that never quits.

According to the official recommendation, the timer will cause memory leak.
It will affect all versions between 3.4.0 and 3.7.0, including 3.2.2
Fixes #10392 #10349
steps to reproduce
Frequent configuration changes can cause memory to keep going up.
The memory goes from 0.2% to 1.7% in few hours


And the memory keeps stable after fixed

Checklist