[asterisk-bugs] [JIRA] (ASTERISK-26516) pjsip: Memory corruption with possible memory leak.

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-26516:
--------------------------------------------

[~alexei gradinari] The 'pept0xf3cf10' pool is used to configure pjproject for operation, grows only on Asterisk startup, must remain for the life of the Asterisk execution, and the log does not capture Asterisk being shut down.  The problem is that memory usage is growing *after* startup.  That pool is not causing the leak.

[~tuxian] The 'auth_cli0x????' pools appear to be leaking.  A new pool is created in the authentication cache for each different authentication realm.

The MALLOC_DEBUG log showed a growth of 179,712 bytes allocated to pjproject pools between the first summary and the last in the log.  That memory corresponds to about 175 auth_cli pools and matches closely with the 184 remaining 'auth_cli0x7fff' pools.  No other remaining pools created after startup represent close to that much memory.

There are also 180 of these lines.
{noformat}
[2016-11-10 16:02:54.489] DEBUG[19397]: pjproject:0 <?>:        sip_auth_clien ...Unable to set auth for tdta0x7fffd4024740: can not find credential for dev.dev.acme.com/Digest
{noformat}

I'd like to see a SIP message log of the registrations (pjsip set logger on) to see what the realm strings are and verify if the realms are changing.  I'll likely need to create another debugging patch to track why these pools are created.

I do appreciate your patience and ability to obtain the needed information.

> pjsip: Memory corruption with possible memory leak.
> ---------------------------------------------------
>
>                 Key: ASTERISK-26516
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26516
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip, Resources/res_pjsip
>    Affects Versions: 13.11.2
>            Reporter: Richard Mudgett
>            Assignee: Richard Mudgett
>         Attachments: 0007_jira_asterisk_26516_v13_free_mem_fix.patch, 2016-10-28.tgz, cli-and-gdb-2016-10-27.tgz, jira_asterisk_26344_v13_committed_fix.patch, jira_asterisk_26344_v13_debuging.patch, jira_asterisk_26516_v13_debugging.patch, jira_asterisk_26516_v13_debugging_v2.patch, screenlog-2016-11-01.tgz, screenlog-2016-11-02.tgz, screenlog-2016-11-03.tgz, screenlog-2016-11-10.tgz
>
>
> This is a continuation of ASTERISK-26344 and ASTERISK-26387 since the original crashes are fixed with patches added to pjproject.  For the setup description look at ASTERISK-26344.



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