Open mys007 opened 7 years ago
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 vectorcollectgarbage()
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.