hazelcast / hazelcast/hazelcast-python-client
Potential memory leak: lock not removed from proxies when the lock is destroyed [API-2129]
オープン
Source: Internal
to-jira
- 主要言語
- Python
- スター
- 116
- フォーク
- 78
- 平均マージ
- 10日 22時間
- マージ済み PR（30日）
- 1
説明
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.
```python
lock = client.cp_subsystem.get_lock("my-distributed-lock").blocking()
fence = lock.lock()
try:
# do something here
pass
finally:
lock.unlock()
lock.destroy() # <-- the lock proxy is not removed from internal proxy data structure
```
コントリビューションガイド
評価
この issue はまだ評価されていません。