[reSIProcate] possible memory leak in resip

Amnon David amnon at hyperms.com
Mon Apr 14 05:43:21 CDT 2008


Hello,

I've noticed there's a slow but steady increase in memory consumption in 
our application when using the resiprocate stack. I've used GlowCode on 
Windows to try and detect where the memory leaks originate and the 
results hint that the stack might be partially responsible. I'm far from 
certain that this is the case and it might very well be some false 
positives, but as this tool helped us detect a memory leak in the 
previous version of resiprocate (which was fixed before we had a chance 
to report it), perhaps it is worth looking into.

The attached file contains the set of locations detected as leaks, with 
the relevant stack trace for each location.

-Amnon

-------------- next part --------------
A non-text attachment was scrubbed...
Name: leaks.zip
Type: application/x-zip-compressed
Size: 6317 bytes
Desc: not available
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20080414/dba3ea18/attachment.bin>


More information about the resiprocate-devel mailing list