[OpenSIPS-Devel] Potential Memory Leak and a Memory Dump

[Bogdan-Andrei Iancu]

Hi Ryan,

Indeed, the dump you provided shows some kind of leak - mainly related 
to body manipulation....To help with the debugging, is is possible to 
get your config file (to see what functions and in what context are used 
?) - if so, please send it privately to me.

Regards,
Bogdan

On 12/29/2011 07:48 PM, Ryan Bullock wrote:
> I believe I am hitting a memory leak in opensips. We receive 'out of
> pkg' memory errors after a few days of runtime, a quick restart of the
> service seems to clean up the problem. I manged to get a memory dump
> from opensips during the last occurance.
>
> System Info:
> Scientific Linux 6
> Linux proxy2 2.6.32-131.21.1.el6.x86_64 #1 SMP Tue Nov 22 14:15:09 CST
> 2011 x86_64 x86_64 x86_64 GNU/Linux
>
> Output of opensips -V:
>
> version: opensips 1.8.0-dev0-notls (x86_64/linux)
> flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST,
> SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
> MAX_URI_SIZE 1024, BUF_SIZE 65535
> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
> svnrevision: 2:8527M
> @(#) $Id: main.c 8506 2011-10-21 10:21:10Z vladut-paiu $
> main.c compiled on 11:04:01 Nov 15 2011 with gcc 4.4.5
>
>
> Opensips command line options:
> -u opensips -g opensips -m 2560 -M 40
>
> Memory Dump Log:
> http://voipnerd.net/files/temp/opensips_memdump.bz2
> (this is rather large, decompresses to around 700mb)
>
> Can anyone provide some advice on how to proceed? I am not entirely
> sure how to interpret the memory dump.
>
> I apologize if this is not the correct list to post to, but it was the
> one listed at http://www.opensips.org/Resources/DocsTsMem
>
> Regards,
>
> Ryan
>
> _______________________________________________
> Devel mailing list
> Devel at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
>


-- 
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
OpenSIPS solutions and "know-how"