Hi,
John, if I run your script I found following behaviour of distinct
backends in terms of memory leaks:
QtAgg - ok
Agg - ok
GTKAgg - oh, memory leak
PDF - ok, as you mentionend
Hope it helps, seems it is not a problem of matplotlib?!
Cheers,
Florian
P.S: I use matplotlib svn with
John, if I run your script I found following behaviour of distinct
backends in terms of memory leaks:
QtAgg - ok
Agg - ok
GTKAgg - oh, memory leak
PDF - ok, as you mentionend
Hi John,
I don't understand whats going on, but when I remove the Line
close(1) from your script and use GTKAgg
On Thu, Jul 3, 2008 at 5:23 AM, Florian Mueller [EMAIL PROTECTED] wrote:
I don't understand whats going on, but when I remove the Line
close(1) from your script and use GTKAgg instead of PDF the
memory leak of my previous post is gone!
Apparently there is a leak in the creation and
I am using matplotlib to produce a big number(16000) of charts and am facing
a steady memory leak. my code sofar looks like:
while(1):
fig=PL.figure(1)
..plot some things..
fig.clf()
PL.close()
am i missing something?
Laurent
On Wed, Jul 2, 2008 at 2:56 PM, laurent oget [EMAIL PROTECTED] wrote:
I am using matplotlib to produce a big number(16000) of charts and am facing
a steady memory leak. my code sofar looks like:
while(1):
fig=PL.figure(1)
..plot some things..
fig.clf()
PL.close()
am i
On Wed, Jul 2, 2008 at 3:20 PM, laurent oget [EMAIL PROTECTED] wrote:
I use the Pdf backend. I did do some digging in the GC module but have not
found anything yet
Please keep all replies on list so others can contribute to the
discussion and future generations of googlers can benefit from it
