arrayfire / arrayfire/arrayfire-python

SIFT memory leak

未关闭
#169 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
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

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。