[asterisk-bugs] [Asterisk 0011080]: SIP channel stops processing calls, but no apparent deadlock

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11080 
====================================================================== 
Reported By:                callguy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11080
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.13  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-24-2007 15:58 CDT
Last Modified:              10-25-2007 10:33 CDT
====================================================================== 
Summary:                    SIP channel stops processing calls, but no apparent
deadlock
Description: 
Approximately once per week we are seeing asterisk stop processing SIP
calls. The behavior is the same as a deadlock, but core show locks does not
show any evidence that there is a deadlock. 

The only way to resolve is to restart asterisk. 

output of:
core show locks
info thread
thread apply all bt

from the running process is attached.
====================================================================== 

---------------------------------------------------------------------- 
 callguy - 10-25-07 10:33  
---------------------------------------------------------------------- 
russell: all of the data here is from a server with DONT_OPTIMIZE and
DEBUG_THREADS both enabled. I suspect you are talking about thread 69,
which I'd agree looks strange. Is there anything else we can do to get you
more information?

we did a lot of testing on the fix for DEBUG_THREADS not being thread
safe, I'm almost wondering if something similar is going on here, though
from what information i could glean it appears to be in a different part of
the code. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-25-07 10:33  callguy        Note Added: 0072502                          
======================================================================