[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:all-tabpanel ]

Richard Mudgett updated ASTERISK-26516:
---------------------------------------

    Attachment: jira_asterisk_26516_v13_debugging_v2.patch

[^jira_asterisk_26516_v13_debugging_v2.patch] - Replaces the earlier [^jira_asterisk_26516_v13_debugging.patch].  The new version removes the grp_lock logging and adds logging for memory pools.  Hopefully, this will give enough information to determine which pool is leaking.

>From an updated and clean workspace install [^jira_asterisk_26516_v13_debugging.patch] and your sip_outbound_registration_perform() {{schedule_registration(state->client_state, (ast_random() % 10) + 1);}} change.

A log capture of 30 min should be enough to have enough leaked memory to identify what pool is leaking.

There is a recent fix that is likely to affect the memory leak which should be merged by the time you are able to test.  https://gerrit.asterisk.org/#/c/4351/

> 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
>
>
> 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)