[asterisk-bugs] [JIRA] (ASTERISK-26516) pjsip: Memory corruption with possible memory leak.
Richard Mudgett (JIRA)
noreply at issues.asterisk.org
Mon Oct 31 18:42:10 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-26516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Mudgett updated ASTERISK-26516:
---------------------------------------
Attachment: 0007_jira_asterisk_26516_v13_free_mem_fix.patch
jira_asterisk_26516_v13_debugging.patch
jira_asterisk_26344_v13_committed_fix.patch
[^jira_asterisk_26344_v13_committed_fix.patch] - This is the actual patch that got committed for ASTERISK-26344. Apply by {{patch -p1 -i <patch-file-name>}}
[^jira_asterisk_26516_v13_debugging.patch] - This is an updated debug message patch that replaces [^jira_asterisk_26344_v13_debugging.patch]. Apply by {{patch -p1 -i <patch-file-name>}}
[^0007_jira_asterisk_26516_v13_free_mem_fix.patch] - Copy this file into the third-party/pjproject/patches directory.
[~tuxian] I'm fairly certain I found the primary cause of the memory corruption. Ironically, it turns out to be a hole in the original fix patch on ASTERISK-26344 which was fixed in the patch that got committed. However, I think there is another potential for corruption that is fixed by [^0007_jira_asterisk_26516_v13_free_mem_fix.patch].
# From a clean workspace apply the three patches
# Run your DNS test with MALLOC_DEBUG. It should be able to go overnight.
I expect the memory leak was another symptom of the bug that was also causing the primary memory corruption.
Please test and report back. Thanks.
> 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
>
>
> 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)
More information about the asterisk-bugs
mailing list