[reSIProcate] potential memory leak on INVITE

[zeljko ancimer]

If I keep sending INVITE requests and not getting any response on them,
there is a significant memory leak.
I'm using reSIProcate 1.4.1 on Windows XP SP3.

To reproduce this problem I modified stackTest example. I am simply sending
INVITE requests in a loop through UDP to localhost. The same result is
obtained regardless if there is a receiver or not for these INVITE requests.
If after some time I stop sending INVITE requests, but continue looping to
call SipStack's process() and receive() methods, memory goes down but not
all is released.

For example, before any INVITE is sent, private bytes used are ~900k. After
19000 INVITEs are sent, private bytes are at ~105M. If I stop sending
INVITEs and keep looping process() and receive() methods for 30 mins,
private bytes are down to ~55M and they stay there.

Am I missing something in the example or is this a real memory leak?

Thanks,
Zeljko
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20081118/1027af66/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: testStack.cxx
Type: application/octet-stream
Size: 2744 bytes
Desc: not available
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20081118/1027af66/attachment.obj>