[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:28 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0107953) aragon (reporter) - 2009-07-20 08:28
 https://issues.asterisk.org/view.php?id=15109#c107953 
---------------------------------------------------------------------- 
This lock info is for 15109

=== 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)

This message is identical to a lock I found when creating ticket
https://issues.asterisk.org/view.php?id=15411
The difference is in 15411 the lock was fatal and that crash occurred on a
production system in * 1.4.24
=== Thread ID: 3085810592 (do_devstate_changes started at [ 363]
devicestate.c ast_device_state_engine_init())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (pbx.c): RDLOCK 6151
ast_rdlock_contexts &conlock
0x8167a40 (2)
=== ---> Lock https://issues.asterisk.org/view.php?id=1 (pbx.c): MUTEX 2034
ast_hint_state_changed
&(&hints)->lock 0x8167c48 (1)
=== ---> Lock https://issues.asterisk.org/view.php?id=2 (chan_sip.c): MUTEX 8843
cb_extensionstate &p->lock
0x8817610 (1)

Something is going on here... although maybe not relevant to 15109 (I have
no idea if they are related, also I have no idea which change in code
removes crashes in revision 206273) 

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