[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-17 08:35 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0107889) aragon (reporter) - 2009-07-17 08:35
 https://issues.asterisk.org/view.php?id=15109#c107889 
---------------------------------------------------------------------- 
I have given up on Valgrind to debug this issue.
Instead I am testing revision 202945.
Also I have ceased using PRI spans for my tests and now I am using a SIP
trunk between Asterisk servers and limiting the number of concurrent
channels on those trunks to 30.  This has reduced the load under testing
from 20-30 to about 5.

In a 24 hour period there has been no MOH crash and no crash as in bug
15396.
This leads me to believe that both issues are caused by locks induced by
high CPU load.
The only trick now is for me to capture any existing locks to a log that
exist EXACTLY before any segfault or I will not get any relevant data to
debug.
Can someone help me with such a debug tool?  I'm looking for a diagnostic
Asterisk patch...
With such a patch I can then control the CPU loads until I can reproduce
the crashes and maybe then find root cause. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-17 08:35 aragon         Note Added: 0107889                          
======================================================================