[asterisk-bugs] [Asterisk 0015109]: [patch] Abort by memory allocator, possibly in moh_files_generator

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Aug 27 22:15:14 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15109 
====================================================================== 
Reported By:                jvandal
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   15109
Category:                   Resources/res_musiconhold
Reproducibility:            random
Severity:                   block
Priority:                   normal
Status:                     ready for testing
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-08-27 22:15 CDT
====================================================================== 
Summary:                    [patch] 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
related to          0015506 Asterisk 1.4.26rc5 (revision 202945 ) d...
related to          0015041 Crash on attended transfer
related to          0015719 Crash in ast_readaudio_callback
parent of           0015396 app_queue segfault
has duplicate       0015195 double free or corruption (!prev) in mo...
has duplicate       0015781 crash: in "ast_fdleak_fclose"...
related to          0015735 Asterisk Chrashes Daily
related to          0015609 WARNING[23025]: channel.c:952 __ast_que...
related to          0015460 Asterisk Crashed When made a attended T...
====================================================================== 

---------------------------------------------------------------------- 
 (0109767) russell (administrator) - 2009-08-27 22:15
 https://issues.asterisk.org/view.php?id=15109#c109767 
---------------------------------------------------------------------- 
kulldominique, I mean not being used.  Being loaded would not matter if you
never played MP3 files.

marhbere, I can't get anything from that backtrace.  Did you compile with
DONT_OPTIMIZE enabled?

All, if you are reporting that are having problems and know that you are
_not_ using format_mp3, can you explicitly verify that you are seeing the
same backtrace as the one posted in the summary of this bug?

A number of crashes have come up here.  Some related, and some are
separate issues.  A lot of times when we get long standing bugs like this,
a single bug report tends to morph into multiple, sometimes.  My immediate
concern with this bug report is fixing the crash shown in the backtrace in
the summary (which has been seen a bunch of times, and in a number of other
bug reports).  There may be other issues that we will need to extract and
handle as separate reports. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-27 22:15 russell        Note Added: 0109767                          
======================================================================




More information about the asterisk-bugs mailing list