Re: [Matplotlib-users] Matplotlib eating memory

2013-10-14 Thread Daniele Nicolodi
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

Re: [Matplotlib-users] Matplotlib eating memory

2013-10-14 Thread Martin MOKREJŠ
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

Re: [Matplotlib-users] Matplotlib eating memory

2013-10-14 Thread Michael Droettboom
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

Re: [Matplotlib-users] Matplotlib eating memory

2013-10-12 Thread Martin MOKREJŠ
Hi, so here is some quick but working example. I added there are 2-3 functions (unused) as a bonus, you can easily call them from the main function using same API (except the piechart). I hope this shows what I lack in matplotlib - a general API so that I could easily switch form scatter plot t

Re: [Matplotlib-users] Matplotlib eating memory

2013-10-10 Thread Martin MOKREJŠ
Hi Ben, thank you for your comments. Looks I will have a bad sleep tonight. :( Some quick answers below. Benjamin Root wrote: > > > > On Thu, Oct 10, 2013 at 10:21 AM, Michael Droettboom > wrote: > > Thanks. This is much more helpful. > > What we need, how

Re: [Matplotlib-users] Matplotlib eating memory

2013-10-10 Thread Benjamin Root
On Thu, Oct 10, 2013 at 10:21 AM, Michael Droettboom wrote: > Thanks. This is much more helpful. > > What we need, however, is a "self contained, standalone example". The > code below calls functions that are not present. See http://sscce.org/for > why this is so important. Again, I would ha

Re: [Matplotlib-users] Matplotlib eating memory

2013-10-10 Thread Michael Droettboom
Thanks. This is much more helpful. What we need, however, is a "self contained, standalone example". The code below calls functions that are not present. See http://sscce.org/ for why this is so important. Again, I would have to guess what those functions do -- it may be relevant, it may no

Re: [Matplotlib-users] Matplotlib eating memory

2013-10-10 Thread Martin MOKREJŠ
Michael Droettboom wrote: > On 10/10/2013 09:47 AM, Martin MOKREJŠ wrote: >> Benjamin Root wrote: >>> >>> >>> On Thu, Oct 10, 2013 at 9:05 AM, Martin MOKREJŠ >> > wrote: >>> >>> Hi, >>>rendering some of my charts takes almost 50GB of RAM. I believe >>> bel

Re: [Matplotlib-users] Matplotlib eating memory

2013-10-10 Thread Martin MOKREJŠ
Benjamin Root wrote: > > On Thu, Oct 10, 2013 at 9:47 AM, Martin MOKREJŠ > wrote: > > Benjamin Root wrote: > > > > > > > > On Thu, Oct 10, 2013 at 9:05 AM, Martin MOKREJŠ

Re: [Matplotlib-users] Matplotlib eating memory

2013-10-10 Thread Michael Droettboom
On 10/10/2013 09:47 AM, Martin MOKREJŠ wrote: > Benjamin Root wrote: >> >> >> On Thu, Oct 10, 2013 at 9:05 AM, Martin MOKREJŠ > > wrote: >> >> Hi, >>rendering some of my charts takes almost 50GB of RAM. I believe below >> is a stracktrace >> of one such

Re: [Matplotlib-users] Matplotlib eating memory

2013-10-10 Thread Martin MOKREJŠ
Michael Droettboom wrote: > Can you provide a complete, standalone example that reproduces the > problem. Otherwise all I can do is guess. > > The usual culprit is forgetting to close figures after you're done with > them. Thanks, I learned that through matplotlib-1.3.0 give spit over me a warn

Re: [Matplotlib-users] Matplotlib eating memory

2013-10-10 Thread Benjamin Root
On Thu, Oct 10, 2013 at 9:47 AM, Martin MOKREJŠ wrote: > Benjamin Root wrote: > > > > > > > > On Thu, Oct 10, 2013 at 9:05 AM, Martin MOKREJŠ mmokr...@gmail.com>> wrote: > > > > Hi, > > rendering some of my charts takes almost 50GB of RAM. I believe > below is a stracktrace > > of

Re: [Matplotlib-users] Matplotlib eating memory

2013-10-10 Thread Martin MOKREJŠ
Benjamin Root wrote: > > > > On Thu, Oct 10, 2013 at 9:05 AM, 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 c

Re: [Matplotlib-users] Matplotlib eating memory

2013-10-10 Thread Benjamin Root
On Thu, Oct 10, 2013 at 9:05 AM, 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 recursio

Re: [Matplotlib-users] Matplotlib eating memory

2013-10-10 Thread Michael Droettboom
Can you provide a complete, standalone example that reproduces the problem. Otherwise all I can do is guess. The usual culprit is forgetting to close figures after you're done with them. Mike On 10/10/2013 09:05 AM, Martin MOKREJŠ wrote: > Hi, >rendering some of my charts takes almost 50GB

[Matplotlib-users] Matplotlib eating memory

2013-10-10 Thread Martin MOKREJŠ
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? The charts had to have 262422 data points in a 2D scatter plo