[asterisk-bugs] [Asterisk 0015808]: 100% Cpu usage when caller hangup while app_dial is executing a Macro

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Sep 17 02:24:22 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15808 
====================================================================== 
Reported By:                mbrancaleoni
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15808
Category:                   Applications/app_dial
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.4.26.1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-09-01 10:56 CDT
Last Modified:              2009-09-17 02:24 CDT
====================================================================== 
Summary:                    100% Cpu usage when caller hangup while app_dial is
executing a Macro
Description: 
If a peer is called using the M option to app_dial, and caller hangup
when peer is on macro, asterisk cpu usage goes 100% until peer closes
the call. After that asterisk still works ok.


====================================================================== 

---------------------------------------------------------------------- 
 (0110859) dcolombo (reporter) - 2009-09-17 02:24
 https://issues.asterisk.org/view.php?id=15808#c110859 
---------------------------------------------------------------------- 
I think that the problem could be in the autoservice_run function
(autoservice.c).
Infact when the caller channel is hangup, while the called peer is on
macro, there is an infinite loop due to this:

if (!x) {
  continue;
}
 
because x var is always 0 in this case. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-17 02:24 dcolombo       Note Added: 0110859                          
======================================================================




More information about the asterisk-bugs mailing list