[asterisk-bugs] [Asterisk 0014322]: MeetMe conference crashes Asterisk 95% of the time when the last user hangs up/exits the conference.

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14322 
====================================================================== 
Reported By:                amessina
Assigned To:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   14322
Category:                   Applications/app_meetme
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.0.3 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-24 01:08 CST
Last Modified:              2009-02-05 17:18 CST
====================================================================== 
Summary:                    MeetMe conference crashes Asterisk 95% of the time
when the last user hangs up/exits the conference.
Description: 
I have a TDM400P card in the box and am using Asterisk-1.6.0.5 (Fedora 10
x86_64).  *Almost* every single time the last user exits a MeetMe
conference, Asterisk segfaults.

Occasionally, Asterisk does not segfault.  I do not use "safe_asterisk."
====================================================================== 

---------------------------------------------------------------------- 
 (0099567) jpeeler (administrator) - 2009-02-05 17:18
 http://bugs.digium.com/view.php?id=14322#c99567 
---------------------------------------------------------------------- 
What version is this happening in? Two are mentioned in the original
report. I don't immediately see what the problem is from the backtrace. I
was hoping I could reproduce it, but haven't been able to do so as of yet. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-05 17:18 jpeeler        Note Added: 0099567                          
======================================================================