← Back to team overview

dolfin team mailing list archive

Memory leak in IntersectionDetector

 

Hi again

One more thing I discovered is that the IntersectionDetector has
a memory leak (probably due to the undeleted GNode pointer).
This is relevant for the new eval function of the DiscreteFunction
class, which initiates an IntersectionDetector everytime the
DiscreteFunction is evaluated at a point. So many calls to the
eval function will eat up the memory!

One more thing. There seems to be a problem with the conversion
of floats in python to reals in C++. When passing a numpy array to
a C++ function through the wrapper, the numbers like e.g. 100.12
are converted to 100 in C++. Has anyone else experienced this behavior?

Kristen


Follow ups