[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-13 12:00 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0107688) aragon (reporter) - 2009-07-13 12:00
 https://issues.asterisk.org/view.php?id=15109#c107688 
---------------------------------------------------------------------- 
Another crash immediately after restarting Asterisk to test a new
revision.
The crash happens immediately after issuing an asterisk restart command.
I see this type of crash often and it appears to be a crash during a
normal load.  The mpg123 error looks suspicious when * crashes...

[root at sip ~]# service asterisk restart
Shutting down asterisk:                                    [  OK  ]
Starting asterisk:                                         [  OK  ]
[root at sip ~]# /usr/sbin/safe_asterisk: line 125:  6208 Segmentation fault 
    (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS}
${ASTARGS} >&/dev/${TTY} < /dev/${TTY}
Asterisk ended with exit status 139
Asterisk exited on signal EXITSTATUS-128.
Automatically restarting Asterisk.
mpg123: no process killed

gdb bt uploaded as gdb07132009.txt 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-13 12:00 aragon         Note Added: 0107688                          
======================================================================