[asterisk-bugs] [JIRA] (ASTERISK-26213) crash at meetme list <confname>: null channel

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231479#comment-231479 ] 

Asterisk Team commented on ASTERISK-26213:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> crash at meetme list <confname>: null channel
> ---------------------------------------------
>
>                 Key: ASTERISK-26213
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26213
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_meetme
>    Affects Versions: 13.8.2
>         Environment: Centos 7
>            Reporter: Tzafrir Cohen
>
> Occasionally there's a crash (backtrace attached) during paging.
> From what I can tell, the crash is caused from running 'meetme list 1466704546847 concise'. It seems at some point there a conference ('user') with no channel associated, and this breaks an assuption or two.
> I tried triggering a race between 'meetme list <name>' and addition / removel of user to meetme. But no luck so far. So I can only hope this fix is correct.



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