[asterisk-bugs] [JIRA] Updated: (ASTERISK-20335) Crash in ast_cel_report_event

[Mark Michelson (JIRA)]

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

Mark Michelson updated ASTERISK-20335:
--------------------------------------

    Attachment: ASTERISK-20335.patch

I have uploaded ASTERISK-20335.patch

This corresponds to a review request I have put on review board at https://reviewboard.asterisk.org/r/2103

This fixes a misuse of channel data during a DTMF-triggered attended transfer. I do not know that this is the same problem that you are experiencing, but the invalid reads that valgrind reported to me were happening for me in {{ast_cel_report_event}}. If you are willing to try it, that would be great. If you do still get a crash with this patch applied, please upload a backtrace from the new crash. Thank you!

> Crash in ast_cel_report_event
> -----------------------------
>
>                 Key: ASTERISK-20335
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20335
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_local
>    Affects Versions: 1.8.16.0
>         Environment: Centos server 5.8x64, 8 core CPU, 8GB RAM
>            Reporter: aragon
>            Assignee: aragon
>            Severity: Critical
>         Attachments: AST18-core-verbose.txt, ASTERISK-20335.patch, asterisk.txt, core show channels.txt, default-dial-cav-joh-002-000918.txt, optimized backtrace.txt, SIP show channels.txt, verbose CLI sip set debug on.txt
>
>
> On a pretty busy system we get deadlocks and crashes daily since installing Asterisk 1.8.16rc1
> Upgraded from 1.8.12 because we were having problems with leaking bye's fixed in ASTERISK-19455
> We were able to collect verbose CLI, core show channels, sip show channels, and Asterisk CLI with sip set debug on.
> Also back traced a core dump file but this is an optimized build since we could not run non-optimized in this environment.
> Including the back trace anyway since it might help diagnose the problem.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira