[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-06-28 12:03 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0107106) aragon (reporter) - 2009-06-28 12:03
 https://issues.asterisk.org/view.php?id=15109#c107106 
---------------------------------------------------------------------- 
mmichelson

How do you want to handle the additional issues exposed by the Valgrind
trace?
I can provide my lab scenario for testing only for a few more weeks... and
I would like to test as many fixes as possible (or until valgrind runs
clean).
I'm sorry for the short window of opportunity but I have to free up some
of these servers.
The lab has been upgraded to r204008 and is currently testing a patch
written for bug 15377

Should I/we open a separate bug report on each issue?
Or I should work with you on iirc...

Could you break down the issues exposed by the Valgrind trace so they can
be documented?  Again I am happy to create another bug report(s) for
this... 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-28 12:03 aragon         Note Added: 0107106                          
======================================================================