No subject

exhausted, and asterisk will be killed/restarted by the watchdog, which in
my case is snmpd.

Seems like most allocations are done around lines 23905 and 23908 in
build_peer() in chan_sip.c

Second file is provided in the zip archive, due to its extremely large
size.

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0018014 large memory consumption of udptl.c module
====================================================================== 

---------------------------------------------------------------------- 
 (0130376) drookie (reporter) - 2011-01-11 07:27
 https://issues.asterisk.org/view.php?id=18027#c130376 
---------------------------------------------------------------------- 
Finally (sorry for keep bothering and not finding the time) I found time to
get sipp and play with the INVITE scenario. Got 2K calls on the * above
(RSS/VSZ) and it's definitely not it. Not leaking.

It's more and more likely that it's REGISTER-related realtime leak. "cause
I'm running HA-clusters on carp, and in case of node failure I got
reregistering interval set to 3 minutes, instead of the common default
(seen on various SIP equipment) of one hour. I will keep on playing with
sipp and I'll try to create a REGISTER scenario for a realtime peer, or at
least something less simple that just the INVITE sequence. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-01-11 07:27 drookie        Note Added: 0130376                          
======================================================================