[asterisk-bugs] [Asterisk 0017230]: app_queue crashes asterisk

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17230 
====================================================================== 
Reported By:                davido
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17230
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.6 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-04-22 11:23 CDT
Last Modified:              2010-05-11 04:19 CDT
====================================================================== 
Summary:                    app_queue crashes asterisk
Description: 
If I call a queue (say, Queue(100)) and hang-up before an agent takes my
call, asterisk doesn't seem to realise that I hung-up and just goes on; the
call stays there, the phone(s) stay(s) ringing and if someone tries to pick
up, asterisk crashes. 

In syslog I see a segfault:

Apr 22 18:13:36 cross-pbx kernel: [  458.006601] asterisk[1141]: segfault
at 36373148 ip 00ee3e81 sp b6f64650 error 4 in asterisk[e8a000+15e000]

Environment:
I'm running Asterisk 1.6.2.5-0ubuntu1 on Ubuntu Lucid
====================================================================== 

---------------------------------------------------------------------- 
 (0121690) davido (reporter) - 2010-05-11 04:19
 https://issues.asterisk.org/view.php?id=17230#c121690 
---------------------------------------------------------------------- 
Sorry for the delay, I have read backtrace.txt and now I have all the
information it's specified there.

By the way, I should mention that this only happens when the call comes
from a Patton Smartnode. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-11 04:19 davido         Note Added: 0121690                          
2010-05-11 04:19 davido         Status                   closed => new       
2010-05-11 04:19 davido         Resolution               suspended => reopened
======================================================================