arrayfire / arrayfire/arrayfire-python

af.features.Features crashes when its __del__ method is called

未关闭
#268 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Python
星标
422
派生
63
PR 合并指标
30 天内没有已合并 PR

描述

When using a `Features()` object, arrayfire crashes silently when calling the object's `__del__()` method if the object's `get_xpos()` method has already been deleted (or has fallen out of scope).

Potentially due to a similar root case as mentioned in #169 (or due to the changes made as a result of this in commit a9031fb5e0db371bc88c958f0b8d43efd7fe8f45)

Running on Windows; using arrayfire 3.8.0.

Minimum working example:
```python
import arrayfire as af

def get_feature_locations(features):
# Get x and y positions of features
x_pos = features.get_xpos()
y_pos = features.get_ypos()

# If this is uncommented, the code works as intended
# return x_pos, y_pos

img = af.randn(d0=500, d1=500)
features, descriptors = af.orb(img, threshold=1, max_features=10, num_levels=1)
feature_locations = get_feature_locations(features)

print("Before delete")
del features
print("After delete")
```

Which outputs:
```
Before delete
```

Uncommenting line 10 (`return x_pos, y_pos`) outputs:
```
Before delete
After delete
```

Thanks!

贡献指南

这个仓库没有索引到贡献指南

调研方向

The reported entry points are af.orb, Features.get_xpos(), Features.get_ypos(), and Features.__del__; first run the provided minimum working example on Windows with ArrayFire 3.8.0. Trace the object lifetime when the position arrays fall out of scope, then verify that deleting features no longer crashes silently and that the returned-position case still works.

由索引模型根据 Issue 内容生成。

评估

技术栈
python
领域
api
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
38/100

把新 issue 发到你的邮箱

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