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
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.
The text was updated successfully, but these errors were encountered:
Somewhat related to this, after getting an array from a feature, say xpos = feature.get_xpos(), there is a double free bug, because the array is cleaned when af_release_features is called in the feature's __del__ and also in the array __del__ method.
Right now, I work around it by setting xpos.arr.value = 0 before the destructors are called.
It's possible to fix this by getting the feature to save a reference to all its arrays, and cleaning them properly. Do you think is a reasonable fix? I'd be happy to open a pull request for it.
It seems that the SIFT detection leaks memory. Here is the example script I am running.
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.
The text was updated successfully, but these errors were encountered: