RE: [reSIProcate] More memory leaks...
These changes have all been checked in now. Some by Kevin Chmilar (Thanks!)
and some by myself. Let me know if there are compile problems on other
OS's.
Thanks,
Scott
-----Original Message-----
From: Scott Godin [mailto:slgodin@xxxxxxxxxxxx]
Sent: Wednesday, May 26, 2004 4:03 PM
To: Alan Hawrylyshen
Cc: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] More memory leaks...
Thanks Alan - the ctor ordering is why I was concerned about the fix for
other compilers.
Also - it Turns out the other leaks weren't that hard to find - you also
need to apply the same fixes (mentioned below) to CountStream.cxx and
MD5Stream.cxx. After doing that I have a stable memory usage!
Once I get confirmation of this fix for other compilers, and the CVS
migration is complete - I will check all of the changes into CVS.
Thanks,
Scott
-----Original Message-----
From: Alan Hawrylyshen [mailto:alan@xxxxxxxxxx]
Sent: Wednesday, May 26, 2004 3:54 PM
To: Scott Godin
Cc: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [reSIProcate] More memory leaks...
On 26 May 2004, at 09:31, Scott Godin wrote:
> I finally got to the bottom of the next leak - it was a tough one to
> find. I'm not sure if it exists or not in other OS's, and I need
> peoples opinions on the best fix for it - to make sure it works on all
> OS's. Here is the problem:
> [snip]
Thanks Scott -- I have some concerns with the order of things in the
proposed ctor, but I suppose we can see if the leak even exists under
Mac OS/X and Linux 1st. If that's not the case, we can just ifdef as
you proposed.
>
> PS. Even with these last two leaks I've posted fixed there still
> seems to be more. Back to the drawing board I guess. Has anyone ever
> tested for memory leaks on other platforms?
>
>
Oh yes -- we are currently in the middle of this, so perhaps we should
take care to post our findings on this list (as should anyone delving
into memory issues) to best co-ordinate our attacks.
IOW, we will post to the list as our performance and memory work start
to reveal issues.
Thanks again.
Cheers,
Alan
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel