Michael Droettboom wrote: > Eric Firing wrote: >> >> I just committed a change to the output formatting of memleak_gui so >> that if you redirect it to a file, that file can be loaded with >> pylab.load() in case you want to plot the columns. (At least this is >> true if you don't use the -c option.) >> > Great. Sorry for stomping on that ;) >> Yesterday, before your commits, I compared memleak_gui with stock >> Python 2.4 versus stock 2.5 (both from ubuntu feisty) and found very >> little difference in the OS memory numbers. > Are they still increasing linearly? I'm still seeing some mystery leaks > with Gtk, Qt4 and (much smaller) on Tk. Qt and Wx seem fine here. Attached are runs with gtk, wx, qtagg, and tkagg. Quite a variety of results: tkagg is best, with only slow memory growth and a constant number of python objects; qtagg grows by 2.2k per loop, with no increase in python object count; wx (which is built on gtk) consumes 3.5k per loop, with an increasing object count; gtk consumes 1.8k per loop with an increasing object count. All runs are on stock ubuntu feisty python 2.5. Eric > Unfortunately Qt4 crashes valgrind, so it's not of much use. > I'm curious whether your results match that. I'm not terribly surprised > that 2.4 isn't different from 2.5, since the case in which entire memory > pools are freed in 2.5 is probably hard to trigger. > > Cheers, > Mike