[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:                   crash
Priority:                   normal
Status:                     feedback
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-05-15 10:27 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
====================================================================== 

---------------------------------------------------------------------- 
 (0104832) aragon (reporter) - 2009-05-15 10:27
 https://issues.asterisk.org/view.php?id=15109#c104832 
---------------------------------------------------------------------- 
When I first reported this problem the time stamp was at night and after
hours.
No one would have issued a reload at that time imho.

But if I had to reproduce based on the reload scenario I think I would try
this...
Run Asterisk under valgrind
Set up a call between two end points and place the call on hold to play
back moh.
issue reload command every 60 seconds for half an hour and post results of
valgrind.

Does this make sense or would the test have to keep running until Asterisk
crash before valgrind could be posted? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-15 10:27 aragon         Note Added: 0104832                          
======================================================================