Possible memory leaks in C-Python Wrappers

[schaubh]

Hi everyone!

I'm experimenting some memory leaks while trying to assign new values to extForceTorqueObject.extForce_B attribute. The same behavior appears if I try to update the Inertia of the S/C object, while the update of the mass doesn't give any problem.
I investigated on the Wrapper of this object (/basilisk/dist3/Basilisk/simulation/extForceTorquePYTHON_wrap.cxx) and in particular on the set method
SWIGINTERN PyObject *_wrap_ExtForceTorque_extForce_B_set(PyObject *SWIGUNUSEDPARM(self), PyObject *args).
Here, I don't see any Py_DECREF for some PyObjects. Could it be the reason causing the memory leaks?
From my understanding, it could be that updating single scalar values is not a problem and memory is correctly freed, while in the other cases (extForceTorqe and Inertia) problems appear because the attributes are not scalars but vectors/matrices.

Thank you!

[schaubh]

Hello Federica,

I've commented out the entirety of _wrap_ExtForceTorque_extForce_B_set so that no variables are defined and the function always returns NULL.
Running while True : module.extForce_B = [1,2,3] from the Python Interpreter (with module being an instance of extForceTorque) leads to a memory usage linearly increasing with time. So there's definitely a memory leak issue somewhere but I don't think it is caused by missing Py_DECREF in _wrap_ExtForceTorque_extForce_B_set

Swig is some sort of a black box to me so this is probably not top notch debugging but that's all I have for the moment. I hope the Basilisk developers can shed some light on this !