[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-20 08:09 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0107952) aragon (reporter) - 2009-07-20 08:09
 https://issues.asterisk.org/view.php?id=15109#c107952 
---------------------------------------------------------------------- 
I have not been able to reproduce a segfault under very high load using SVN
revision 206273.  In fact there were no segfaults at all with this SVN
release...
However, while capturing lock data for the last 72 hours I noticed a
consistent lock message that occurs constantly.  Asterisk doesn't appear to
lock or stop processing calls although there appears to be some delay in
processing audio.
The most consistent lock is "(autoservice.c): MUTEX 89 autoservice_run
&(&aslist)->lock 0x8179948 (1)".  That message appears in almost every core
show locks output.

Is this lock info unusual or does it indicate any problems?


=======================================================================
=== Currently Held Locks ==============================================
=======================================================================
===
=== <file> <line num> <function> <lock name> <lock addr> (times locked)
===
=== Thread ID: 3085396880 (do_devstate_changes  started at [  363]
devicestate.c ast_device_state_engine_init())
=== ---> Tried and failed to get Lock https://issues.asterisk.org/view.php?id=0
(channel.c): MUTEX 1128
channel_find_locked &c->lock 0x8e771c8 (0)
=== -------------------------------------------------------------------
===
=== Thread ID: 3050437520 (autoservice_run      started at [  238]
autoservice.c ast_autoservice_start())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (autoservice.c): MUTEX
89 autoservice_run
&(&aslist)->lock 0x8179948 (1)
=== -------------------------------------------------------------------
===
=== Thread ID: 2882485136 (pbx_thread           started at [ 2626] pbx.c
ast_pbx_start())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (channel.c): MUTEX 1493
ast_hangup &chan->lock 0x8e771c8
(1)
=== ---> Tried and failed to get Lock https://issues.asterisk.org/view.php?id=1
(chan_local.c): MUTEX 575
local_hangup &p->chan->lock 0xa64db18 (0)
=== -------------------------------------------------------------------
===
=== Thread ID: 2890775440 (pbx_thread           started at [ 2626] pbx.c
ast_pbx_start())
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=0
(autoservice.c): MUTEX 263
ast_autoservice_stop &(&aslist)->lock 0x8179948 (1)
=== --- ---> Locked Here: autoservice.c line 89 (autoservice_run)
=== -------------------------------------------------------------------
===
=== Thread ID: 2825239440 (pbx_thread           started at [ 2626] pbx.c
ast_pbx_start())
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=0
(autoservice.c): MUTEX 263
ast_autoservice_stop &(&aslist)->lock 0x8179948 (1)
=== --- ---> Locked Here: autoservice.c line 89 (autoservice_run)
=== -------------------------------------------------------------------
===
=== Thread ID: 2926230416 (pbx_thread           started at [ 2626] pbx.c
ast_pbx_start())
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=0
(autoservice.c): MUTEX 263
ast_autoservice_stop &(&aslist)->lock 0x8179948 (1)
=== --- ---> Locked Here: autoservice.c line 89 (autoservice_run)
=== -------------------------------------------------------------------
===
=== Thread ID: 2836298640 (pbx_thread           started at [ 2626] pbx.c
ast_pbx_start())
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=0
(autoservice.c): MUTEX 263
ast_autoservice_stop &(&aslist)->lock 0x8179948 (1)
=== --- ---> Locked Here: autoservice.c line 89 (autoservice_run)
=== -------------------------------------------------------------------
===
=== Thread ID: 2837281680 (pbx_thread           started at [ 2626] pbx.c
ast_pbx_start())
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=0
(autoservice.c): MUTEX 263
ast_autoservice_stop &(&aslist)->lock 0x8179948 (1)
=== --- ---> Locked Here: autoservice.c line 89 (autoservice_run)
=== ------------------------------------------------------------------- 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-20 08:09 aragon         Note Added: 0107952                          
======================================================================