fix: prevent memory leak by periodically cleaning up expired cache entries #671
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 ExtendedClient cache implementation was only replacing expired entries when the exact same object was requested again. Different objects (secrets and object stores) were continuously being added to the cache slice but never removed, causing unbounded memory growth.
Partially Fixes: #385
Tagging as partial fix given that this is very minor given that the objects rarely change