[asterisk-bugs] [Asterisk 0012744]: AGI 100% CPU utilization (deadlock?)

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12744 
====================================================================== 
Reported By:                reallost1
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12744
Category:                   Core/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0-beta8 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-28-2008 14:56 CDT
Last Modified:              05-30-2008 15:58 CDT
====================================================================== 
Summary:                    AGI 100% CPU utilization (deadlock?)
Description: 
Asterisk threads use 100% CPU when trying to spawn an AGI process.
It happens with multple different AGI scripts.
It happens several times per hour and has multiple threads that need to be
killed manually.

>core show channels
SIP/67.55..xxx-08 4352941645 at default:9 Up      AGI(agirunner)             
  
SIP/xxx..xxx-0894f000  8 at podcast-menu:1     Up      AGI(bored)   

When the threads are killed, the channels hangup.
====================================================================== 

---------------------------------------------------------------------- 
 reallost1 - 05-30-08 15:58  
---------------------------------------------------------------------- 
I have been connecting to the stuck thread directly with gdb to get the
backtrace.  This time I attached to the master process and did a thread
apply all bt full as requested.  It is uploaded as "bt full thread" 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-30-08 15:58  reallost1      Note Added: 0087581                          
======================================================================