[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:                     acknowledged
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-07-02 09:50 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
has duplicate       0015195 double free or corruption (!prev) in mo...
====================================================================== 

---------------------------------------------------------------------- 
 (0107342) aragon (reporter) - 2009-07-02 09:50
 https://issues.asterisk.org/view.php?id=15109#c107342 
---------------------------------------------------------------------- 
My valgrind ran for two days with several reported memory errors in file. 
Except that additional flags were needed to make the file more useful.

I restarted asterisk with valgrind again and it crashed before beginning
call processing.  To be honest I don't know if it is common for Asterisk to
crash while starting under Valgrind.  So I am posting the full valgrind
output with all required flags "valgrindcrashg07022009allflags.txt"

Next I started valgrind again with all required flags and I will allow
this to run for several hours and will upload that valgrind file later. 
This I hope will allow a developer to see where the memory issues are and
will get us a patch(es).
I don't expect anything to crash under valgrind since I expect this is a
race condition in Asterisk that will not appear when running under
Valgrind... 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-02 09:50 aragon         Note Added: 0107342                          
======================================================================