This tries a bunch of potential causes of a memory leak in gidden/cyclopts.

A plotting script is provided that can plot the results for any of the following tests. For example, one can plot the results pttest.py by :

$ ./pttest.py > out
$ ./plt.py out
$ eog fig.png

An arbitrary number of files can be plotted against each other, e.g. :

$ ./pttest.py > out.pt
$ ./pttest-np.py > out.np
$ ./plt.py out.pt out.np
$ eog fig.png

This is not the cause. To replicate run:

$ xdress --debug
$ ./setup.py build
$ ./memtest.py

Play around with the N value in memtest and un/comment the gc.collect() call inside of the loop. If you are running h/top you'll see that the memory resources are cleaned up correctly.

This test definitely mem leaks. This uses the table row object and the memory leak seems to be fairly fast. Run this test with:

$ ./pttest.py

This test uses the table append() method rather than the row object. It also directly appends numpy arrays. This may have a minor memory leak but it is much slower. Run this test with:

$ pttest-np.py

The row attr should probably be avoided, not just because it is slow!