[asterisk-bugs] [Asterisk 0015951]: core show locks stop responding and crash asterisk

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15951 
====================================================================== 
Reported By:                atis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15951
Category:                   Core/General
Reproducibility:            have not tried
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1.5 
JIRA:                        
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-09-24 06:55 CDT
Last Modified:              2009-09-24 09:08 CDT
====================================================================== 
Summary:                    core show locks stop responding and crash asterisk
Description: 
I had bunch of testing calls running, but i saw some weird things with
queue, so i wanted to check for deadlocks. Issuing "core show locks"
returned empty result (no lock headers at all) for few times, and then it
hanged for a minute and crashed.
 
====================================================================== 

---------------------------------------------------------------------- 
 (0111317) atis (reporter) - 2009-09-24 09:08
 https://issues.asterisk.org/view.php?id=15951#c111317 
---------------------------------------------------------------------- 
It is not optimized:

MENUSELECT_CFLAGS=DONT_OPTIMIZE DEBUG_THREADS LOADABLE_MODULES
G711_NEW_ALGORITHM G711_REDUCED_BRANCHING DEBUG_CHANNEL_LOCKS MALLOC_DEBUG

Well, about backtraces, it helps others to search for similar crash. But
probably yes, this time I posted too much of stack :) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-24 09:08 atis           Note Added: 0111317                          
======================================================================