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

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Jul 2 11:58:26 CDT 2009


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-02 11:58 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0107351) aragon (reporter) - 2009-07-02 11:58
 https://issues.asterisk.org/view.php?id=15109#c107351 
---------------------------------------------------------------------- 
Uploading valgrind output from a few hours of testing.
There is lots of good data here since all flags were enabled in Valgrind.

mmichelson can you take a look please?
there are two files uploaded of interest
valgrindcrash07022009allflags.txt (Asterisk crashed under valgrind during
reload)
valgrindnocrash07022009withflags.txt (Asterisk did not crash but core show
locks was very interesting; indicating some locking on unused PRI channel)

=======================================================================
=== Currently Held Locks ==============================================
=======================================================================
===
=== <file> <line num> <function> <lock name> <lock addr> (times locked)
===
=== Thread ID: 72186768 (accept_thread        started at [ 3297] manager.c
init_manager())
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=0 (manager.c):
MUTEX 2452 accept_thread
&(&sessions)->lock 0x817e768 (1)
=== --- ---> Locked Here: manager.c line 2589 (manager_event)
=== -------------------------------------------------------------------
===
=== Thread ID: 113474448 (do_monitor           started at [16810]
chan_sip.c restart_monitor())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (chan_sip.c): MUTEX
16756 do_monitor &monlock 0x6bf8e20
(1)
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=1 (manager.c):
MUTEX 2589 manager_event
&(&sessions)->lock 0x817e768 (1)
=== --- ---> Locked Here: manager.c line 2589 (manager_event)
=== -------------------------------------------------------------------
===
=== Thread ID: 121052048 (pri_dchannel         started at [10045]
chan_dahdi.c start_pri())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (chan_dahdi.c): MUTEX
9022 pri_dchannel &pri->lock
0x70e1de4 (1)
=== -------------------------------------------------------------------
===
=== Thread ID: 121297808 (pri_dchannel         started at [10045]
chan_dahdi.c start_pri())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (chan_dahdi.c): MUTEX
9022 pri_dchannel &pri->lock
0x70e2b1c (1)
=== -------------------------------------------------------------------
===
=== Thread ID: 121543568 (pri_dchannel         started at [10045]
chan_dahdi.c start_pri())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (chan_dahdi.c): MUTEX
9022 pri_dchannel &pri->lock
0x70e3854 (1)
=== -------------------------------------------------------------------
===
=== Thread ID: 121789328 (pri_dchannel         started at [10045]
chan_dahdi.c start_pri())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (chan_dahdi.c): MUTEX
9022 pri_dchannel &pri->lock
0x70e458c (1)
=== -------------------------------------------------------------------
===
=== Thread ID: 74152848 (session_do           started at [ 2522] manager.c
accept_thread())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (manager.c): MUTEX 2169
process_events
&s->session->__lock 0x5b03f44 (1)
=== -------------------------------------------------------------------
===
=== Thread ID: 74398608 (session_do           started at [ 2522] manager.c
accept_thread())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (manager.c): RDLOCK 2281
process_message &actionlock
0x81855e0 (1)
=== -------------------------------------------------------------------
===
=== Thread ID: 150969232 (pbx_thread           started at [ 2657] pbx.c
ast_pbx_start())
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=0 (manager.c):
MUTEX 2589 manager_event
&(&sessions)->lock 0x817e768 (1)
=== --- ---> Locked Here: manager.c line 2589 (manager_event)
=== -------------------------------------------------------------------
===
=== Thread ID: 132287376 (pbx_thread           started at [ 2657] pbx.c
ast_pbx_start())
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=0 (manager.c):
MUTEX 2589 manager_event
&(&sessions)->lock 0x817e768 (1)
=== --- ---> Locked Here: manager.c line 2589 (manager_event)
=== -------------------------------------------------------------------
===
=== Thread ID: 133024656 (pbx_thread           started at [ 2657] pbx.c
ast_pbx_start())
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=0 (manager.c):
MUTEX 2589 manager_event
&(&sessions)->lock 0x817e768 (1)
=== --- ---> Locked Here: manager.c line 2589 (manager_event)
=== -------------------------------------------------------------------
===
=== Thread ID: 149986192 (pbx_thread           started at [ 2657] pbx.c
ast_pbx_start())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (manager.c): MUTEX 2589
manager_event &(&sessions)->lock
0x817e768 (1)
=== -------------------------------------------------------------------
===
=== Thread ID: 150723472 (pbx_thread           started at [ 2657] pbx.c
ast_pbx_start())
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=0 (manager.c):
MUTEX 2589 manager_event
&(&sessions)->lock 0x817e768 (1)
=== --- ---> Locked Here: manager.c line 2589 (manager_event)
=== -------------------------------------------------------------------
===
======================================================================= 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-02 11:58 aragon         Note Added: 0107351                          
======================================================================




More information about the asterisk-bugs mailing list