Summary: | ASTERISK-22802: MeetMe: crash when ast_check_hangup is called on a NULL conference channel | ||
Reporter: | Grace Okafor (wendixx) | Labels: | |
Date Opened: | 2013-11-01 05:25:14 | Date Closed: | 2018-01-02 08:44:28.000-0600 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | Applications/app_meetme |
Versions: | 1.8.23.0 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | CentOS 5.8, 64bit System, 2GB RAM, | Attachments: | ( 0) backtrace.txt |
Description: | I installed an application Web-meetme on the server. I schedule a conference, which works well, I can login one user. but when a second user tries to join the conference, it gives the error:
{noformat} /usr/sbin/safe_asterisk: line 145: 1732 Segmentation fault (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} > /dev/${TTY} 2>&1 < /dev/${TTY} Asterisk ended with exit status 139 Asterisk exited on signal 11. Automatically restarting Asterisk. {noformat} After checking severally online for a solution, I decided to submit the issue here. Thanks | ||
Comments: | By: Grace Okafor (wendixx) 2013-11-01 05:35:30.363-0500 This is My backtrace result. Thanks By: Matt Jordan (mjordan) 2013-11-01 10:19:46.232-0500 It appears as if somehow {{conf->chan}} is NULL when it enters into a {{while}} loop that calls {{ast_check_hangup}} repeatedly. In general, I would have expected that {{conf->chan}} is non-NULL at that point, particularly if the system has been configured correctly with DAHDI. By: Grace Okafor (wendixx) 2013-11-12 09:21:48.895-0600 Hi Matt, Is there a way for me to rectify this Please? By: Joshua C. Colp (jcolp) 2017-12-18 11:25:49.101-0600 Have you experienced this under the current supported version of Asterisk? As well app_meetme is considered extended support, with app_confbridge replacing it. By: Asterisk Team (asteriskteam) 2018-01-02 08:44:28.380-0600 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines |