[asterisk-bugs] [JIRA] (ASTERISK-26836) Potential PJSIP Memory Leak

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235545#comment-235545 ] 

Asterisk Team commented on ASTERISK-26836:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> Potential PJSIP Memory Leak
> ---------------------------
>
>                 Key: ASTERISK-26836
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26836
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 13.11.2, 13.14.0
>         Environment: Centos 6, PJSIP 2.4.5
>            Reporter: Daniel Journo
>            Severity: Critical
>
> This is a recurring issue on all my production servers. When it happens, Asterisk stops serving SIP clients properly.
> It reads to me as a memory leak as it's just one character incrementing.
> The latest time, it occurred shortly (but not immediately) after I issued a 'pjsip reload', but it may have just been a coincidence. I've included the timing in the CLI log.
> Seems to happen every 4 or 5 days requiring a 'killall -9 asterisk' and 'database deltree registrar' in order to get working again. I can't remember, but the first time it happened, Asterisk would not respond to 'core stop now' or 'core restart now' so I had to do killall. But I havent tried 'core stop now' during subsequent issues.



--
This message was sent by Atlassian JIRA
(v6.2#6252)