On 10/10/2013 15:05, Martin MOKREJŠ wrote:
> Hi,
> rendering some of my charts takes almost 50GB of RAM. I believe below is a
> stracktrace
> of one such situation when it already took 15GB. Would somebody comments on
> what is
> matplotlib doing at the very moment? Why the recursion?
>
> Th
Michael Droettboom wrote:
> Sorry to repeat myself, but please reduce this to a short, self contained
> example, that is absolutely minimal to demonstrate the problem.
> http://sscce.org/ should help better explain what I'm after. I don't want to
> find the needle in the haystack here -- the
2013/10/14 Mark Lawrence :
> On 14/10/2013 13:51, OCuanachain, Oisin (Oisin) wrote:
>> Hi,
>>
>> I am having problems with a script. It runs a number of iterations and
>> plots and saves a number of plots on each iteration. After the plots
>> have been saved I issue the pyplot.close(‘all’) command
On 2013/10/14 8:26 AM, OCuanachain, Oisin (Oisin) wrote:
>
>
> Hi Eric,
>
> If .emf is no longer supported in current versions of matplotlib is
> there an alternative SVG-type format I can use ? I use .emf because I
> find that it tends to produce the clearest plots independent of how I
> re-size
-Bunteachtaireacht-
From: Eric Firing [mailto:efir...@hawaii.edu]
Sent: 14 October 2013 19:09
To: matplotlib-users@lists.sourceforge.net
Subject: Re: [Matplotlib-users] Maidir le: Memory leak when using pyplot.ion() ?
On 2013/10/14 7:48 AM, OCuanachain, Oisin (Oisin) wrote:
> Hi Mike,
>
On 2013/10/14 7:48 AM, OCuanachain, Oisin (Oisin) wrote:
> Hi Mike,
>
> ion(), ioff() are useful to get immediate feedback when developing a
> script, when it is fully debugged I then increase the number of
> iterations and leave it running over the weekend. At that point I could
> obviously also h
I see you are using matplotlib 1.0.1. There have been several memory leak
bugs fixed since then, so I would suggest upgrading. I also notice you are
using the "emf" backend for saving figures. If I remember correctly, that
backend has been deprecated (or maybe even removed) in the latest release
(v
On 14/10/2013 13:51, OCuanachain, Oisin (Oisin) wrote:
> Hi,
>
> I am having problems with a script. It runs a number of iterations and
> plots and saves a number of plots on each iteration. After the plots
> have been saved I issue the pyplot.close(‘all’) command so despite many
> plots being crea
Hi Mike,
ion(), ioff() are useful to get immediate feedback when developing a script,
when it is fully debugged I then increase the number of iterations and leave it
running over the weekend. At that point I could obviously also have removed
ion(), ioff() but given that I had no idea that this
Sorry to repeat myself, but please reduce this to a short, self
contained example, that is absolutely minimal to demonstrate the
problem. http://sscce.org/ should help better explain what I'm after. I
don't want to find the needle in the haystack here -- there is code in
your example that does
I haven't had a chance to look into where the memory is actually
leaking, ion/ioff are intended for interactive use, and here you are
saving a large number of plots to files. Why do you need ion at all?
Mike
On 10/14/2013 08:51 AM, OCuanachain, Oisin (Oisin) wrote:
Hi,
I am having problems
Hi,
I am having problems with a script. It runs a number of iterations and plots
and saves a number of plots on each iteration. After the plots have been saved
I issue the pyplot.close('all') command so despite many plots being created
only 4 should be open at any given time which should not ca
12 matches
Mail list logo
