Hello,
I looked quickly to the core and seems ok, I will check the accounting
later.
Do you simply account $ai or is any other attribute related to it?
If you have time to test, can you put the $ai in an avp during the
request processing and account that avp? If the leak is not shown
anymore in that case, it narrows down a lot where to look at.
Cheers,
Daniel
On 4/17/13 5:19 PM, Tais Plougmann Hansen wrote:
Hi,
I'm seeing a possible leak in parsing the P-Asserted-Identity, and
possibly P-Preferred-Identity headers in kamailio-3.3.4.
I have a server running in which one thread has currently most of the
8 MB private memory allocated. At restart qm_sums reports parse_pai.c
as sitting on most of the memory:
Apr 16 16:38:58 gws1 /usr/sbin/kamailio[9398]: INFO: qm_status: heap
size= 8388608
Apr 16 16:38:58 gws1 /usr/sbin/kamailio[9398]: INFO: qm_status: used=
5369240, used+overhead=6417216, free=1971392
[...]
Apr 16 16:39:03 gws1 /usr/sbin/kamailio[9398]: INFO: qm_sums: count=
6198 size= 4721776 bytes from <core>: parse_pai.c: parse_pai_header(58)
I am currently using the header through $ai for xlog statements, the
accounting module and a validity check (if (!($(ai{uri.user}) =~
"^\+[1-9]+")) {...}).
From digging through the logs it could seem like this happens when
using $ai in the accounting module. I'll try removing it from
accounting (log_extra) and see if it stops leaking.
--
Tais Plougmann Hansen
OSD Consulting ApS
osd.dk <http://osd.dk/>
Tel: +45 78101078 <tel:%2B45%2078101078>
CVR: DK31332737
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -
http://www.asipto.com
http://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
Kamailio World Conference, April 16-17, 2013, Berlin
-
http://conference.kamailio.com -