Memory leak about blensor HOT 3 CLOSED

Hi Peter,

thanks for the info. I will first upgrade to the latest Blender 2.63a and check if the memory leak comes from there.
However I guess it has to do with some changes in the blender codebase from 2.60 to 2.63 that require changes to blensor.

That's going to be quite some "fun" to track down :)

from blensor.

Ok, i've committed several fixes. The memory leaks should be back to a normal level ;) I can't guarantee that there aren't still some parts that are not freed properly but I ran a kinect scan over 23 frames and the memory usage did not increase from the first to the last frame.

The problem is that the blender core is not properly documented, so doing the right thing is not always instantly clear. In addition it seems that the mathutils module of blender does not free the objects properly. I changed the whole code to keep use of that modules at a minimum.

Furthermore blender does no longer complain about unfreed blocks when it exits, so at least blender itself thinks that no memory is lost.

One side effect of this refactoring is that the sensors (especially those who produce many points, depthmap/kinect/tof camera) are faster than before

Can you verify this?

from blensor.

Yep, I've given it a try and the the issue seems to be resolved now. Thanks!

from blensor.