e() with each loop iteration.
>
> 40MB per image doesn't sound way out of reason to me. How big are your
> images?
> """
>
> On 10/05/2009 03:46 AM, Leo Trottier wrote:
>
> Hi,
>
> I think I've figured out what's going on. It's a com
to use it
> again.) The best route is to call close('all') or fig.close() with each
> loop iteration.
>
> 40MB per image doesn't sound way out of reason to me. How big are your
> images?
>
> Mike
>
>
> On 10/01/2009 10:25 PM, Leo Trottier wrote:
>
I have a friend who's having strange memory issues when opening and
displaying images (using Matplotlib).
Here's what he says:
###
pylab seems really inefficient: Opening a few images and displaying them
eats up tons of memory, and the memory doesn't get freed.
Hi,
Did anyone have any insight on this? Alternatively, anyone know why there
has been little uptake on this question ...(apologies that it was
accidentally sent twice)?
Leo
On Tue, Feb 3, 2009 at 11:42 PM, Leo Trottier wrote:
> Matplotlib 0.98.5.2
> Location: C:\leo\.matplotlib
>
Matplotlib 0.98.5.2
Location: C:\leo\.matplotlib
Running Windows XP SP2
Obtained from pythonxy v. 2.1.10
No rc customizations ...
I've been having a devil of a time getting my rcParams to update
mid-script. Perhaps this isn't possible, but if that's so, it's not
entirely clear. Even if it is so,
Matplotlib 0.98.5.2
Location: C:\leo\.matplotlib
Running Windows XP SP2
Obtained from pythonxy v. 2.1.10
No rc customizations ...
I've been having a devil of a time getting my rcParams to update
mid-script. Perhaps this isn't possible, but if that's so, it's not
entirely clear. Even if it is so,
