[asterisk-bugs] [Asterisk 0015109]: Abort by memory allocator, possibly in moh_files_generator

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15109 
====================================================================== 
Reported By:                jvandal
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15109
Category:                   Resources/res_musiconhold
Reproducibility:            random
Severity:                   block
Priority:                   normal
Status:                     feedback
Target Version:             1.4.27
Asterisk Version:           1.4.24 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-05-14 10:49 CDT
Last Modified:              2009-08-18 13:42 CDT
====================================================================== 
Summary:                    Abort by memory allocator, possibly in
moh_files_generator
Description: 
I have a server running with Asterisk 1.4.24.1 where it randomly segfault
for "unknown" reason.

I'm not sure if this is related to moh_files_generator function or with
filestream_descructor.

Let me know what needed in order to fix this crash, if GDB traces aren't
enough. 

Asterisk is compiled with DONT_OPTIMIZE and others flag needed for "gdb".

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0014958 Segfault Asterisk 1.4.24.1
related to          0015123 out of bounds crash and core dump
related to          0015506 Asterisk 1.4.26rc5 (revision 202945 ) d...
parent of           0015396 app_queue segfault in revision 202945
has duplicate       0015195 double free or corruption (!prev) in mo...
====================================================================== 

---------------------------------------------------------------------- 
 (0109230) aragon (reporter) - 2009-08-18 13:42
 https://issues.asterisk.org/view.php?id=15109#c109230 
---------------------------------------------------------------------- 
I think we are dealing with a memory leak caused by reloads while files
based moh is in use. While I watch the system with htop installed I can see
roughly 100MB of RAM is leaked on my test setup per hour.  As the memory
reaches critical the swap reaches 2GB.
As I said in the past I could not get Asterisk to crash under valgrind.  I
think this has to do with the swap file and the large amount of RAM
available.
While in valgrind the memory has more time to free... and we avoid the
memory abort. 

My server had 4GB of ram installed so I brought this figure down to get a
crash with Valgrind.
Anyway, long story short: Asterisk locked before it could crash so I am
uploading valgrind18092009.txt
Memory usage reached 950/1010 while capturing this output.  I hope the
details of the leak are captured in this text file...  I'm running another
valgrind setup in hopes of catching this in a crash. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-18 13:42 aragon         Note Added: 0109230                          
======================================================================