arrayfire / arrayfire/arrayfire-python
SIFT memory leak
- 主要言語
- Python
- スター
- 422
- フォーク
- 63
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
It seems that the SIFT detection leaks memory. Here is the example script I am running.
```python
import arrayfire as af
import time
while True:
im = af.load_image('image.jpg')
feats, desc = af.vision.sift(im)
af.device.device_gc()
af.print_mem_info()
time.sleep(1)
```
I solved part of the leaks in #168. Apparently the features destructor wasn't called, and af_release_features needed to be called explicitly from python.
With this fix the ORB feature detection works without leaks, but SIFT and GLOH still do.
Running pretty much the same methods in C works without a memory leak. So I think there might be another destructor that ought to be called explicitly, just like af_release_features, but I could not figure out where the leak was originated from.
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
調査の方向性
Start by reproducing the supplied loop with af.load_image, af.vision.sift, af.device.device_gc, and af.print_mem_info, then compare its behavior with the C implementation and the ORB result described in the issue. Trace the feature cleanup around af_release_features and the SIFT/GLOH bindings; done means repeated detection no longer shows memory growth.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- python
- 領域
- backend, performance
- issue の種類
- バグ
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 35/100