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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15808 
====================================================================== 
Reported By:                mbrancaleoni
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   15808
Category:                   Applications/app_dial
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Target Version:             1.6.2.15
Asterisk Version:           SVN 
JIRA:                       SWP-1144 
Regression:                 No 
Reviewboard Link:            
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:              2010-09-24 06:58 CDT
====================================================================== 
Summary:                    [patch] 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.


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

---------------------------------------------------------------------- 
 (0127363) tbelder (reporter) - 2010-09-24 06:58
 https://issues.asterisk.org/view.php?id=15808#c127363 
---------------------------------------------------------------------- 
Could this issue be related to https://issues.asterisk.org/view.php?id=17564?

What dcolombo describes about:
if (!x) {
  continue;
}

is fixed in this case with a sleep of 10 msecs in the loop. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-09-24 06:58 tbelder        Note Added: 0127363                          
======================================================================