[asterisk-bugs] [JIRA] (ASTERISK-26835) res_rtp_asterisk: Crash when freeing RTCP address string

[scgm11 (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-26835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

scgm11 updated ASTERISK-26835:
------------------------------

    Attachment: example.mp3
                core-asterisk-running-2017-04-03T09-07-25-0400-full.txt
                core-asterisk-running-2017-04-03T09-07-25-0400-thread1.txt
                core-asterisk-running-2017-04-03T09-07-25-0400-locks.txt
                core-asterisk-running-2017-04-03T09-07-25-0400-brief.txt

With the latest patch I had some rtp issues, having the calls with cuts (seems like missing packets), I attach all logs and an mp3, all calls were the same and going back to a previous version solve the issue.

> res_rtp_asterisk: Crash when freeing RTCP address string
> --------------------------------------------------------
>
>                 Key: ASTERISK-26835
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26835
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_rtp_asterisk
>    Affects Versions: 13.14.0
>         Environment: Debian 8
>            Reporter: Niklas Larsson
>            Assignee: Richard Mudgett
>         Attachments: 0001-res_rtp_asterisk-Set-rtp-rtcp-to-NULL-to-prevent-dou.patch, backtrace_20170306_clean.txt, backtrace_core.uc51-2017-03-17T08-34-30+0100.txt, backtrace_core.uc62-2017-03-02T11-47-33+0100.txt, core-asterisk-running-2017-03-31T09-33-43-0400-brief.txt, core-asterisk-running-2017-03-31T09-33-43-0400-full.txt, core-asterisk-running-2017-03-31T09-33-43-0400-locks.txt, core-asterisk-running-2017-03-31T09-33-43-0400-thread1.txt, core-asterisk-running-2017-04-03T09-07-25-0400-brief.txt, core-asterisk-running-2017-04-03T09-07-25-0400-full.txt, core-asterisk-running-2017-04-03T09-07-25-0400-locks.txt, core-asterisk-running-2017-04-03T09-07-25-0400-thread1.txt, example.mp3
>
>
> Now and then we get this segfaults and it has have been around for some versions (at least 13.13 could be before as well).



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