[asterisk-bugs] [Asterisk 0018890]: Error obtaining mutex in channel.c

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18890 
====================================================================== 
Reported By:                absystech
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18890
Category:                   Core/Channels
Reproducibility:            sometimes
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.16.2 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-02-25 08:49 CST
Last Modified:              2011-02-25 08:59 CST
====================================================================== 
Summary:                    Error obtaining mutex in channel.c
Description: 
Core crash after incoming calls on DAHDI or on transfer between incoming
calls on DAHDI and SIP peers.

SIP Account 5630 is a receptionist phone and it intercept incoming calls
wich arrive in the queue called "Standard".
Maybe it crashes on a transfert between 5630 and 7662, maybe on incoming
calls...
====================================================================== 

---------------------------------------------------------------------- 
 (0132408) davidw (reporter) - 2011-02-25 08:59
 https://issues.asterisk.org/view.php?id=18890#c132408 
---------------------------------------------------------------------- 
Although I can't view the log without going to a bit of trouble (Unix
newlines but viewing on Windows), this sort of symptom (invalid lock
followed by delayed, memory corruption, crash) is often caused by a race
involving a hangup on one or both conflicting channels. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-02-25 08:59 davidw         Note Added: 0132408                          
======================================================================