Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 Fix ClusterCacheTracker memory leak #9543

Commits on Jan 26, 2024

  1. Fix ClusterCacheTracker memory leak

    Decouple the code that creates uncached client from the code that
    creates the cached client. This way, we don't start the cache until
    the cached client is created.
    
    This avoids scenarios where the `ClusterCacheTracker` cache is started
    when only an uncached client is needed.
    
    There is an existing code path, described in the original issue, where
    the `ClusterCacheTracker` cache is started when only an uncached client
    is needed. The cache is re-created later, and the initial cache is
    still running continuously in the background.
    
    Signed-off-by: Ionut Balutoiu <ionut@balutoiu.com>
    ionutbalutoiu committed Jan 26, 2024
    Configuration menu
    Copy the full SHA
    97534b8 View commit details
    Browse the repository at this point in the history