[asterisk-bugs] [JIRA] Feedback Requested: (ASTERISK-16710) memory leak in chan_sip.c

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-16710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-16710:
-----------------------------------

    Assignee: Eugene M. Zheganin
      Status: Waiting for Feedback  (was: Open)

> memory leak in chan_sip.c
> -------------------------
>
>                 Key: ASTERISK-16710
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-16710
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Channels/chan_sip/General
>            Reporter: Eugene M. Zheganin
>            Assignee: Eugene M. Zheganin
>         Attachments: 2010-01-27_growth.pdf, bt-coredump.txt, invitetest.xml, leaking-additional-info-no-T.38.txt, leaking-allocations-additional-no-T.38.zip, leaking-allocations.zip, leaking.txt, subscribetest.inf.txt
>
>
> chan_sip.c is still constantly leaking memory.
> Below 2 files are provided: one, leaking.txt, showing the output of 'memory show summary/core show calls uptime', in which allocations count and size in chan_sip.c grow over time; second, leaking-allocations.txt, showing the final output of 'memory show allocations'.
> The 'summary' file is started with 293358 bytes and 300 allocations, and is ended with 55402745 bytes and 105513 allocations. The RSS of the asterisk process is 187M at the end of observation and continues to grow. From my experience, memory usage willgrow until all of the server memory is 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.
> ****** ADDITIONAL INFORMATION ******
> asterisk is running on the FreeBSD 8.0-RELEASE-p2. this is a production pbx, with more than 2K calls per day.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira