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 have observed a memory leak in Indices filled by KdTree.radiusSearch() or KdTree.nearestKSearch() and read by Indices.viewAsTensor() afterwards. Calling an explicit storage():free() on the obtained tensor's storage then seems necessary.
The text was updated successfully, but these errors were encountered:
Hi @mys007! Thanks for reporting the issue. Do you have a little code snippet that reproduces the leak? Calling storage():free() on the Tensor returned by Indices.viewAsTensor() should normally not be necessary because the Tensor is just a view into internal vector memory, no real copy of the data (see indices.cpp). Have you checked that a no longer referenced object will not be freed by a collectgarbage() call?
I have observed a memory leak in Indices filled by
KdTree.radiusSearch()
orKdTree.nearestKSearch()
and read byIndices.viewAsTensor()
afterwards. Calling an explicitstorage():free()
on the obtained tensor's storage then seems necessary.The text was updated successfully, but these errors were encountered: