[asterisk-bugs] [Asterisk 0016053]: Crash on deeply nested while/if statements in AEL

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16053 
====================================================================== 
Reported By:                diLLec
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16053
Category:                   PBX/pbx_ael
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1.6 
JIRA:                       SWP-1414 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-10-11 17:49 CDT
Last Modified:              2010-06-10 13:03 CDT
====================================================================== 
Summary:                    Crash on deeply nested while/if statements in AEL
Description: 
While reloading ael via ael reload the asterisk process runs into SIGSEGV. 

This bug is curios since Asterisk starts and loads the ael very well. Also
if ael reload is typed in at the cli when starting Asterisk with -c is
working fine.

The issue only shows up when using asterisk manager or asterisk -r.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0017430 segfault in for loop embedded switch st...
====================================================================== 

---------------------------------------------------------------------- 
 (0123254) murf (manager) - 2010-06-10 13:03
 https://issues.asterisk.org/view.php?id=16053#c123254 
---------------------------------------------------------------------- 
Yes, there are big implications! Asterisk, when idle, runs several threads,
each for some separate purpose. During call processing, new threads are
created. You have to make sure that all these threads added together do not
exhaust the supply of virtual memory, with each thread getting so much
larger a space... It might be better to increase the number from the
original value slightly until the problem goes away. Then add in a
percentage for safety, and try running that way. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-10 13:03 murf           Note Added: 0123254                          
======================================================================