shared axes.
so I thought that part was resolved already...
JDH
I use a modified version of the script Laurent Oget posted (see
attachment). Here is the output if I don't comment out PL.close(1).
~/python/test$ python looptest.py -dGTK
0 GC 69354 69354 0 13854
100 GC 84354 150 0
I think i narrowed down the memory leak i have been chasing for a while.
If i remove the call to twinx i get a slow leak, which would cause me
trouble
after a very long time. With the call to twinx, however i am losing
thousands of objects
at each loop.
Thanks,
Laurent
import pylab as PL
def
(t,st)
fig.clf()
PL.close(1)
gc.collect()
print GC
print len(gc.get_objects())
print len(gc.garbage)
looptest()
2008/7/11 laurent oget [EMAIL PROTECTED]:
I think i narrowed down the memory leak i have been chasing for a while.
If i remove the call
I am using matplotlib to produce a big number(16000) of charts and am facing
a steady memory leak. my code sofar looks like:
while(1):
fig=PL.figure(1)
..plot some things..
fig.clf()
PL.close()
am i missing something?
Laurent
