Summary:	ASTERISK-26213: app_meetme: crash at meetme list <confname>: null channel
Reporter:	Tzafrir Cohen (tzafrir)	Labels:
Date Opened:	2016-07-19 05:18:01	Date Closed:
Priority:	Minor	Regression?
Status:	Open/New	Components:	Applications/app_meetme
Versions:	13.8.2	Frequency of Occurrence
Related Issues:
Environment:	Centos 7	Attachments:	( 0) 26213_nullchan.patch ( 1) asterisk_crash_bt_20162306.txt
Description:	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.
Comments:	By: Asterisk Team (asteriskteam) 2016-07-19 05:18:02.041-0500 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]. By: Tzafrir Cohen (tzafrir) 2016-07-19 05:20:02.012-0500 Backtrace of the crash By: Tzafrir Cohen (tzafrir) 2016-07-19 05:21:44.211-0500 A suggested fix. Untested. By: Joshua C. Colp (jcolp) 2016-07-20 12:21:33.074-0500 Do you have the prior console log to the crash to see what the state of things were? By: Tzafrir Cohen (tzafrir) 2016-07-21 02:16:35.402-0500 No. I don't have any logs.