Re: Re: Memleak in canvas_paint, update

> Hi Al,
>     Thanks for the code! I was able to find two or three more leaks,
>     and 
> I committed the changes to cvs. I'm sure that there are some leaks 
> related to pango, but that's probably because I'm using an old version 
> here. Tell me what you find. Saludos,
> <ADRIAN>
>

Adrian,

Hey, you nailed it!  I've run my app for a couple of hours, and memory has 
grown only a very small amount.  I have to do more analysis, but I believe 
the growth is related to my adding points to the plot.  If I can attribute 
it to that, you may have taken care of *all* the leaks down this call 
path.  Even if there are a couple small ones left, I think the rate of 
memory footprint growth would not cause me problems for many, many days at 
a time anyway.  I'll know the answer to that in the next couple of days 
after I can dig deeper in and make sure the growth is related to what I'm 
doing on the plot(s).

I *truly* appreciate you digging in to this, and staying on it to chase 
these leaks down.  Thanks!!

-Al




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/