On 5/17/06, Colin Whittaker <[EMAIL PROTECTED]> wrote:
I think I have traced my growing memory size down to msg headers which seem to multiply on each REGISTER refresh and SUBSCRIBE refresh. It appears these headers are removed with msg_header_remove(), but not freed. Shouldn't msg_header_remove() free the removed headers ?
The removed headers might be used for something useful (like request routing within a proxy or B2BUA)...
If not, it seems like the calling routine should free them since they are no longer necessary. These headers are not really lost, since they are allocated with their home pointing to the du_msg object in the ds_usage object of the handle, but the memory will continue to grow until the handle is destroyed.
I think the problem is that original message is used as the request message. What should happen is that we should use the copy of the original message when refreshing, not a reference to it. I'll runa a bit longer test and see if the refresh still leaks memory. -- Pekka.Pessi mail at nokia.com ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Sofia-sip-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
