[asterisk-bugs] [Asterisk 0017564]: Asterisk "locks up" the system when an external process is called from the 'h' extension with a lower priority than Asterisk.

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17564 
====================================================================== 
Reported By:                ramonpeek
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17564
Category:                   Resources/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.33 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-06-29 05:47 CDT
Last Modified:              2010-06-29 07:32 CDT
====================================================================== 
Summary:                    Asterisk "locks up" the system when an external
process is called from the 'h' extension with a lower priority than Asterisk.
Description: 
We noticed that Asterisk "locks up" the system when an external process is
called from the 'h' extension with a lower priority than Asterisk.
This issue is a follow up on issue:
https://issues.asterisk.org/view.php?id=16349

See Additional Information Field for more info....
====================================================================== 

---------------------------------------------------------------------- 
 (0124010) ramonpeek (reporter) - 2010-06-29 07:32
 https://issues.asterisk.org/view.php?id=17564#c124010 
---------------------------------------------------------------------- 
At first our system would become fully unresponsive, that's why I listed
this issue at "crash". Just recently I've found ways to make the system
"not-crash" on this issue.

I'll try to get to get a GDB trace during the worst kind of "lock-up" I
can replicate without having the system become fully unresponsive...
To be continued... 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-29 07:32 ramonpeek      Note Added: 0124010                          
======================================================================