matplotlib-users

[Matplotlib-users] Still a memory leak in matplotlib?

[Foehn <fo...@po...>]

I am using the matplotlib, basemap and numpy versions delivered with 
Ubuntu 12.04. I know the versions are outdated and should be replaced by 
something new. But I do not want to install "alien" versions, because 
sometimes you can run into problems with dependencies and so on.

My problem now is a more elaborated basemap application that dies of 
memory hunger in course of the time. I have  a workaround that splits 
the program into chunks small enough not to die. For several reasons his 
is not ideal.

I condensed the memory leak problem for my machine down to a rudimentary 
program. My question to the community with up to date 
(LINUX-)maplotlibs: Does it still cause a memory problem or not. If 
"yes" I will stick to my old matplotlib version, if "no" I consider a 
change.

The Program can be found here:

https://www.wuala.com/Foehn/Sonstiges/testmplmemleak/?key=nEhr83BTW4tx


Thanks for the help,
Föhn

Re: [Matplotlib-users] Still a memory leak in matplotlib?

[Remo G. <su...@li...>]

Hi Föhn,

By default, the pyplot interface (recall that it is a Matlab-like state 
machine) does not release a figure's memory. You need to do this by hand 
by calling the clf() method after every plot you make:
...
plt.close()
plt.clf()

Stackoverflow contains a few threads about the subject.

Best,
Remo



On 30.03.2014 13:33, Foehn wrote:
> I am using the matplotlib, basemap and numpy versions delivered with
> Ubuntu 12.04. I know the versions are outdated and should be replaced by
> something new. But I do not want to install "alien" versions, because
> sometimes you can run into problems with dependencies and so on.
>
> My problem now is a more elaborated basemap application that dies of
> memory hunger in course of the time. I have  a workaround that splits
> the program into chunks small enough not to die. For several reasons his
> is not ideal.
>
> I condensed the memory leak problem for my machine down to a rudimentary
> program. My question to the community with up to date
> (LINUX-)maplotlibs: Does it still cause a memory problem or not. If
> "yes" I will stick to my old matplotlib version, if "no" I consider a
> change.
>
> The Program can be found here:
>
> https://www.wuala.com/Foehn/Sonstiges/testmplmemleak/?key=nEhr83BTW4tx
>
>
> Thanks for the help,
> Föhn
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Re: [Matplotlib-users] Still a memory leak in matplotlib?

[Foehn <fo...@po...>]

plt.clf()

solved all my problems. I simply did not notice this simple solution. 
Whenever I saw "memory leak" there was given the advice to upgrade older 
versions.

Thanks a lot,
Foehn

Am 2014-03-30 13:55, schrieb Remo Goetschi:
> Hi Föhn,
>
> By default, the pyplot interface (recall that it is a Matlab-like state
> machine) does not release a figure's memory. You need to do this by hand
> by calling the clf() method after every plot you make:
> ...
> plt.close()
> plt.clf()
>
> Stackoverflow contains a few threads about the subject.
>
> Best,
> Remo
>
>