John Hunter wrote: > On 3/26/07, Jeff Whitaker <[EMAIL PROTECTED]> wrote: >> John Hunter wrote: > >> John: Nope, that has no effect. What does cla clean up that clf doesn't? > > Well, it flushes all the lines, removes the ticks, that kind of thing. > But fig.clear sets > > self.axes = [] > > so if there are no references to the axes anywhere, gc.collect() > should force a clean up and a purging of all the axes artists. Ie, it > should matter if Axes.cla does self.lines=[] if the figure clear > removes all references to the axes. I'm wondering if someone > somewhere in mpl is keeping a reference to the axes....
It would have to be something like a growing list of axes, wouldn't it? Otherwise the old axes would be replaced by the new one on the next run through the loop, and it would not be a leak. (The other leak, with interactive backends and nothing but pylab.figure(); pylab.close() in the loop is also keeping me baffled. It is not the same as the above, but it is the same sort of thing.) Are there any python debugging tools that can show at the python level where memory is being used? Eric ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
