[asterisk-bugs] [Asterisk 0016608]: [patch] Deadlock on &(&channels)->lock

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16608 
====================================================================== 
Reported By:                sergee
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   16608
Category:                   Channels/General
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     feedback
Target Version:             1.6.0.28
Asterisk Version:           SVN 
JIRA:                       SWP-732 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.0 
SVN Revision (number only!): 237060 
Request Review:              
====================================================================== 
Date Submitted:             2010-01-14 15:04 CST
Last Modified:              2010-04-16 09:28 CDT
====================================================================== 
Summary:                    [patch] Deadlock on &(&channels)->lock
Description: 
I've got 2 deadlocks in 3 days. It happens in a peak hours, with more then
a hundred calls in the system.

I've got 2 files 1 with "core show locks" - from the first deadlock (the
day before yesterday), second file - with output from gdb (intho thread,
thread apply all bt, thread apply all bt full) - from today's deadlock.
====================================================================== 

---------------------------------------------------------------------- 
 (0120541) tilghman (administrator) - 2010-04-16 09:28
 https://issues.asterisk.org/view.php?id=16608#c120541 
---------------------------------------------------------------------- 
1)  It's not a deadlock.  It's a resource starvation caused by holding a
lock while waiting for RTP to be received.  Since no RTP is received, the
lock is held forever.  Now I think you understand why my patch did not
introduce an RTP timeout:  it was already inherent in your system.

2)  No, you see RTP _sent_ from Asterisk, but in certain cases (most?),
you aren't _receiving_ RTP.  That's what's causing the timeout.

I want to see the SIP traces for calls both where you ARE receiving RTP
(X-Lite) as well as calls for which you are not (Zoiper), so I can figure
out what is specifically different. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-16 09:28 tilghman       Note Added: 0120541                          
======================================================================