[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 16:54 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
====================================================================== 

---------------------------------------------------------------------- 
 (0104863) mmichelson (administrator) - 2009-05-15 16:54
 https://issues.asterisk.org/view.php?id=15109#c104863 
---------------------------------------------------------------------- 
The valgrind output here doesn't have anything related to the filestream
refcount problem in it, unfortunately. It just has the typical libc startup
errors.

We had a customer seeing this issue a little while back, and it was
impossible for me to reproduce it while running valgrind. I did a lot of
code inspection and I could not figure out how this particular problem
could be happening.

lmadsen: you say you were able to reproduce this by doing some reloading
of moh? I actually did not try doing that during my tests. I may revisit
this since I was very frustrated that I could not see how the crash could
be happening. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-15 16:54 mmichelson     Note Added: 0104863                          
======================================================================