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

[Alexei Gradinari (JIRA)]

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

Alexei Gradinari commented on ASTERISK-26516:
---------------------------------------------

The 'pept0xf3cf10' pool increased rapidly.
This poll is used for ast_pjsip_endpoint which never released.

{noformat}
[2016-11-10 14:58:30.049] DEBUG[18993]: pjproject:0 <?>:          pept0xf3cf10 Pool: created, size=4096
...
[2016-11-10 14:58:30.553] DEBUG[18993]: pjproject:0 <?>:          pept0xf3cf10 Pool: 584 bytes requested, resizing pool by 4000 bytes (used=5413984, cap=5416096)
{noformat}


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