[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=196723#comment-196723 ] 

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

Two things

1) Looking at your logs, I see messages like:

{noformat}
[2012-08-29 12:19:44] WARNING[2799] chan_sip.c: Autodestruct on dialog '36142e6e-e7e7e10b-18ec8044 at 192.168.2.179' with owner in place (Method: BYE). Rescheduling destruction for 10000 ms
{normormat}

This is indicative of a channel reference leak, and unfortunately it's not easy to pinpoint where this might be happening. One potential cause of this is that an AGI may not be exiting properly, therefore holding onto a channel forever. There are other potential corner cases for this sort of thing as well. I recently opened ASTERISK-20375, where I have figured out an odd case using transfers and local channels that results in a channel reference leak. While the steps to reproduce are really bizarre, I imagine that the same reference leak could be triggered through more conventional means as well.

2) Once I started bringing transfers into the mix, I was able to get valgrind to start spewing errors in {{ast_cel_report_event()}} when I attempt to do an attended transfer. I suspect that this could be the same root cause of the crash you are seeing. I'm going to look into it a bit more to try to find the source of the problem. Basically, it appears that a channel being passed to {{ast_cel_report_event()}} has already been freed. Thus attempting to access that channel's data is causing invalid read errors in valgrind.

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