You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating for visibility in case people think this is worth taking forward.
When you destroy a lock that lock is not removed CPProxyManager._lock_proxies resulting in a potential memory leak in long running clients that may otherwise destroy a number of locks. Obviously, usual caveats around such destruction.
lock=client.cp_subsystem.get_lock("my-distributed-lock").blocking()
fence=lock.lock()
try:
# do something herepassfinally:
lock.unlock()
lock.destroy() # <-- the lock proxy is not removed from internal proxy data structure
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Potential memory leak: lock not removed from proxies when the lock is destroyed
Potential memory leak: lock not removed from proxies when the lock is destroyed [API-2129]
Sep 4, 2023
Creating for visibility in case people think this is worth taking forward.
When you
destroy
a lock that lock is not removedCPProxyManager._lock_proxies
resulting in a potential memory leak in long running clients that may otherwise destroy a number of locks. Obviously, usual caveats around such destruction.The text was updated successfully, but these errors were encountered: