On Mon, Jul 14, 2008 at 3:05 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote: > I can confirm this. > > Commenting out "del Gcf.figs[num]" in Gcf.destroy (in _pylab_helpers.py) > also seems to resolve the leak. But I have no idea why, so I won't > commit it just yet. I don't have much time to look deeper now. Does > anyone (who probably understands figure management better than me) have > an idea what might cause this?
Can you post the script you are using to test -- I am a little confused from reading this thread by whether or not twinx is implicated. Also, I saw that you committed some changes vis-a-vis the twinx leak r5747 | mdboom | 2008-07-11 13:21:53 -0500 (Fri, 11 Jul 2008) | 2 lines Fix memory leak when using shared axes. so I thought that part was resolved already... JDH ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
