Re: [reSIProcate] potential memory leak on INVITE
This is probably just due to the kernel not aggressively reclaiming
memory. Leaks can also be caused if your test program doesn't send
responses to the requests it gets.
Best regards,
Byron Campen
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
<testStack.cxx>_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel