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

[Asterisk Bug Tracker]

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:             2008-05-28 14:56 CDT
Last Modified:              2008-09-11 22:34 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0092395) reallost1 (reporter) - 2008-09-11 22:34
 http://bugs.digium.com/view.php?id=12744#c92395 
---------------------------------------------------------------------- 
I believe this to be an OS issue in the threading libraries.  I have
upgraded the OS and am not having this trouble anymore. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-09-11 22:34 reallost1      Note Added: 0092395                          
======================================================================