[asterisk-bugs] [Asterisk 0016942]: 100% CPU load at feature startup

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16942 
====================================================================== 
Reported By:                UJvu
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16942
Category:                   Core/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1.16 
JIRA:                       SWP-989 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 249534 
Request Review:              
====================================================================== 
Date Submitted:             2010-03-02 03:21 CST
Last Modified:              2010-03-03 13:32 CST
====================================================================== 
Summary:                    100% CPU load at feature startup
Description: 
1. 251 calls 250
2. 250 picks up and talks to 251
3. 250 dials *5, feature tr1 starts, 250 hangs up
4. 252 rings (macro-new_redirect)
5. 252 picks up and talks to 251
6. end of call

Points 4-6 has 100% cpu load
====================================================================== 

---------------------------------------------------------------------- 
 (0118893) lmadsen (administrator) - 2010-03-03 13:32
 https://issues.asterisk.org/view.php?id=16942#c118893 
---------------------------------------------------------------------- 
This is likely expected behaviour, per the note in features.conf.sample:

; IMPORTANT NOTE: The applicationmap is not intended to be used for all
Asterisk
;   applications. When applications are used in extensions.conf, they are
executed
;   by the PBX core. In this case, these applications are executed outside
of the
;   PBX core, so it does *not* make sense to use any application which has
any
;   concept of dialplan flow. Examples of this would be things like Macro,
Goto,
;   Background, WaitExten, and many more.
;
; Enabling these features means that the PBX needs to stay in the media
flow and
; media will not be re-directed if DTMF is sent in the media stream.
 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-03 13:32 lmadsen        Note Added: 0118893                          
2010-03-03 13:32 lmadsen        Status                   acknowledged =>
feedback
======================================================================