On Thu, Apr 21, 2011 at 2:07 PM, Michael Droettboom wrote:
> Ok. I think I've found a leak in the way the spines' paths were being
> updated.
>
> https://github.com/matplotlib/matplotlib/pull/89
>
> Can you apply the patch there and let me know how it improves things for
> you?
>
> Cheers,
> Mike
On Wed, Apr 20, 2011 at 1:04 PM, Michael Droettboom wrote:
> On 04/20/2011 11:27 AM, Caleb Constantine wrote:
>> On Wed, Apr 20, 2011 at 9:29 AM, Michael Droettboom wrote:
>>> On 04/20/2011 07:48 AM, Caleb Constantine wrote:
>>>> On Tue, Apr 19, 2011 at 2:25 PM, Mic
On Wed, Apr 20, 2011 at 9:29 AM, Michael Droettboom wrote:
> On 04/20/2011 07:48 AM, Caleb Constantine wrote:
>> On Tue, Apr 19, 2011 at 2:25 PM, Michael Droettboom wrote:
>>> Ok. I have a RHEL5 Linux box with Python 2.7.1.
>>>
>>> With Numpy 1.4.1 and 1.5.
On Tue, Apr 19, 2011 at 2:25 PM, Michael Droettboom wrote:
> Ok. I have a RHEL5 Linux box with Python 2.7.1.
>
> With Numpy 1.4.1 and 1.5.1 I don't see any leaks. With Numpy git HEAD,
> I did see a leak -- I submitted a pull request to Numpy here:
>
> https://github.com/numpy/numpy/pull/76
>
>
On Tue, Apr 19, 2011 at 1:01 PM, Michael Droettboom wrote:
> There's a lot of moving parts here. Running your script again is
> showing some leaks in valgrind that weren't there before, but a number
> of the underlying libraries have changed on my system since then (memory
> leaks tend to be Whac
This picks up from a thread of the same name between 18 Nov 2010 and
22 Nov 2010.
Release 1.0.1 of matplotlib has made significant gains in reducing the
memory leak (thanks!!), but it did not
eliminate the problem entirely. Recall, the TkAgg back-end does not
have any leak, so we know this particu
Matplotlib Users:
It seems matplotlib plotting has a relatively small memory leak. My
experiments suggest it leaks between 5K and 8K bytes of RAM for ever plot
redraw. For example, in one experiment, plotting the same buffer (so as to
not
allocate new memory) every second for a period of about 12
