[asterisk-bugs] [JIRA] Commented: (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:comment-tabpanel&focusedCommentId=196918#comment-196918 ] 

Mark Michelson commented on ASTERISK-20335:
-------------------------------------------

{quote}
Mark, should I be expecting another patch based on those warnings?
{quote}

Not on this issue report. I'm trying to limit the scope of this report to the CEL crash. As far as I know, the two problems are not directly related. I opened a separate issue for the channel reference leak that I found, and while I cannot say for sure, I'd be willing to believe that you are seeing the same problem as me (both problems are based on DTMF *2 transfers). If I were you, I'd watch that issue (ASTERISK-20375) and try whatever patch gets posted there.

> 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, autodestruct.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