Memory leak - unreachable references to reader about laspy HOT 5 CLOSED

An easy fix would be to just delete the objects, that holds these references in the Reader.close method...

from laspy.

I'll try to prepare a pull request. Would also be nice to avoid creating FileManager.point_refs until absolutely necessary. E.g. when memory mapping a las file with 500 million points, it takes a long time, and a lot of memory to generate this list. Will see if I can handle that somehow.

from laspy.

Correction:
The circular references do seem to be collectable (no del method). However the garbage collector does seem to be a bit slow in doing this... So no worries :-)

from laspy.

Sorry for the delayed reply, glad you got it figured out. The del methods which were previously included were actually causing a lot of the previous problems, as they overloaded the default destructors.

from laspy.

No problem :-) Yes - as I understand it, del methods will prevent automatic garbage collection of unreachable objects. Now they should be collected, eventually...

I have fiddled a little with helping the garbage collector by deleting objects with circular references in the Reader / Write close methods. And also trying to avoid the call to build_point_refs in FileManager.get_points, which will construct a long list using which does not seem to be used. Might open a pull request.

from laspy.