[sr-dev] How to catch a mem leak

[Carlos Ruiz Díaz]

Hello Jon,

There's a guide you can follow to troubleshoot memory problems:
http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:memory

Also, please check memdbg and memlog:
http://kamailio.org/dokuwiki/doku.php/core-cookbook:3.1.x#memdbg

Regards.

Carlos.

On Wed, Oct 31, 2012 at 8:55 AM, Jon Bonilla <manwe at aholab.ehu.es> wrote:

> Hi all
>
> I'm using diferent versions of kamailio 3.3 in production environment. In 2
> cases I've found what I suspect to be a mem leak in the parser.
>
> In my scenarios, there's a stateless proxy in front of a stateful one. Both
> run on the same machine and both handle the same traffic (except the one
> rejected by the sl one). So my guess is that the parser has the mem leak
> somewhere because the difference is the malformed messages rejected by the
> first proxy.
>
> Both have the same pkg and shm options.
>
> The stateless one runs out of mem. shm mem and pkg mem grow until kamailio
> runs
> out of mem. I have generated coredumps of the sl processes with kill -6
> when the
> mem was about to run out but I can't see anything useful there.
>
> My question is, how can I debug this? Build kamailio with different flags?
> Increase mem verbosity? It takes several days until it runs out of mem and
> I'd
> like to catch it soon.
>
>
>
>
> thanks,
>
> Jon
>
>
> _______________________________________________
> sr-dev mailing list
> sr-dev at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20121031/58c42800/attachment.htm>