I had a quick peek on the code and I'm not sure what is the reason of
the memory consumption. Please note that the SIP stack keeps a copy of
each BYE request and response for 30 seconds, just in case there is
retransmission. The copy of request could be freed, but in expense of
copying more data when transaction object is created.

I would guess there might be some fragmentation issues. Using my test
setup the memory consumption seems to stabilize at 13 Meg and then
starts slowly decresing. The call rate is roughly 30 calls/second,
there was 850 transactions in memory. 15 kB per call is a bit on the
high side.

--
Pekka.Pessi mail at nokia.com

Hello once again,

Thanks for answering my doubts... however, I the problem remains. You have tried exactly the code I have supplied on the mailing list? Because running that same test, memory starts climbing up to 40 megs and further... ( by the way, by simply starting the program I have a mem consumption of 12 megs )

I have let the following test run for the past 12 hours:
30 calls/second
Each call lasts 30 seconds
900 concurrent calls

Surprisingly, memory consumption did stabilize, at 74 megs! However, I have finished the calls and absolutely no memory was freed meaning that having those 900 concurrent calls or none is taking up same amount of memory... how can this be? I am even using your handle debug and it's showing me that all handles are destroyed but there's still no memory freed.
Is there a way to 'force' this memory to be freed? I'd really appreciate some help here...

Perhaps also giving some detailed information on how memory is managed when receiving an invite, etc., could help me out figuring what to do...

Thanks again,
Tiago
_______________________________________________
Sofia-sip-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel

Reply via email to