Hi Justin, On 30/11/16 20:11, Justin Chang wrote:
Hi all,
What's the best way or tool to detect for potential memory leaks for Firedrake? Normally I use the PETSc log functions but in my Firedrake code I am doing lots of extra curricular programming which isn't seen by PETSc.
"It's difficult" You can, in the normal way, use valgrind. But you have to build a custom Python install so that valgrind doesn't report lots of false positives. Normally, python objects will just be garbage-collected in the normal way. The worry is if you "accidentally" keep around references to them in various places. I think at the moment we're not doing so in firedrake itself, but maybe we've broken something again. Are you experiencing memory leaks, or is this more "idle" curiosity? Lawrence