Re: Memory leaks
Michael Droettboom wrote:
> Eric Firing wrote:
>> So, this test is still showing problems, with similar memory
>> consumption in these three backends.
> Not necessarily. By default, Python allocates large pools from the
> operating system and then manages those pools itself (though its
> PyMalloc call). Prior to Python 2.5, those pools were never freed.
> With Python 2.5, empty pools, when they occur, are freed back to the
> OS. Due to fragmentation issues, even if there is enough free space in
> those pools for new objects, new pools may need to be created anyway,
> since Python objects can't be moved once they are created. So seeing
> modest increases in memory usage during a long-running Python
> application is typical, and not something that can be avoided
> wiinaccurate at finding memory leaksthout micro-optimizing for pool
> performance (something that may be very difficult). If memory usage is
> truly increasing in an unbounded way, then, yes, there may be problems,
> but it should eventually stabilize (though in a test such as memleak_gui
> that may take many iterations). It's more interesting to see the curve
> of memory usage over time than the average over a number of iterations.
I agree. I just ran 2000 iterations with GtkAgg, plotted every 10th
point, and the increase is linear (apart from a little bumpiness) over
the entire range (not just the last 1000 iterations reported below):
Backend GTKAgg, toolbar toolbar2
Averaging over loops 1000 to 2000
Memory went from 31248k to 35040k
Average memory consumed per loop: 3.7920k bytes
Maybe this is just the behavior of pymalloc in 2.5?
(Continue reading)
I can probably look at this Monday, but if you want to > commit and test some of these before then, please do so. Done. It looks like there is still plenty of memory leakage, but there are improvements, and the huge list of uncollectable garbage with tkAgg is gone. I also made memleak_gui.py more flexible with arguments. For example, here are tests with three backends, a generous number of loops, and suppression of intermediate output: python ../unit/memleak_gui.py -d wx -s 500 -e 1000 -q uncollectable list: []
Greetings,
Norbert
John Hunter wrote:
> On 6/30/07, Norbert Nemec <
RSS Feed