Ok. Thanks, I'll look into it. Just wanted to rule out that this wasn't the known Gtk memory leak with old versions of Gtk before devoting time to it.
Cheers, Mike Eric Firing wrote: > Michael Droettboom wrote: >> Can you provide more information about the platform and backend that >> you are using? > > Mike, > > I was able to reproduce this with my ubuntu 8.10, gtkagg backend. I > ran the code via cut and paste with the stock python interpreter, not > ipython. I did not measure the memory use carefully, but used the > system monitor to observe memory for that process climbing, maybe 500k > per cycle. > > Our usual memleak tester shows no problem, however. > > Eric > >> >> D2Hitman wrote: >>> I am getting a memory leak when i am using the pylab.close() >>> function. I am >>> running matplotlib-0.98.3. It happens in a very simple script such as: >>> >>> #!/usr/bin/python >>> import time >>> import pylab >>> >>> while True: >>> time.sleep(1) >>> print 'calling pylab' >>> pylab.box() >>> pylab.close() >>> >>> Every close seems to store megabytes in physical memory. Any idea >>> why this >>> happens? >>> >>> Cheers. >>> >>> >>> >> > -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
