[asterisk-bugs] [Asterisk 0019125]: Deadlocks on 1.6.2.17.2

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19125 
====================================================================== 
Reported By:                viniciusfontes
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19125
Category:                   PBX/General
Reproducibility:            unable to reproduce
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.17.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-04-15 09:31 CDT
Last Modified:              2011-05-11 15:51 CDT
====================================================================== 
Summary:                    Deadlocks on 1.6.2.17.2
Description: 
Getting deadlocks on 1.6.2.17.2. I suspect MixMonitor() is causing them,
but I'm not sure. Unfortunely I couldn't get a backtrace, but the output of
'core show locks' is attached below.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0018654 [patch] [regression] Call Pickup Hangs ...
====================================================================== 

---------------------------------------------------------------------- 
 (0134811) lmadsen (administrator) - 2011-05-11 15:51
 https://issues.asterisk.org/view.php?id=19125#c134811 
---------------------------------------------------------------------- 
Reopening after testing from rmudgett leads us to believe this is not a
duplicate of the other issue. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-05-11 15:51 lmadsen        Note Added: 0134811                          
2011-05-11 15:51 lmadsen        Status                   closed => new       
2011-05-11 15:51 lmadsen        Resolution               duplicate => reopened
======================================================================