[asterisk-bugs] [Asterisk 0011972]: tls transport often causes asterisk to lock

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11972 
====================================================================== 
Reported By:                pj
Assigned To:                jamesgolovich
====================================================================== 
Project:                    Asterisk
Issue ID:                   11972
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   block
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 103313 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-11-2008 11:04 CST
Last Modified:              02-17-2008 23:46 CST
====================================================================== 
Summary:                    tls transport often causes asterisk to lock
Description: 
when asterisk is locked, no call or registration is processed,
this happened several times today and yesterday (tried several trunk
revisions)
currently haven't found thing, what causes the locking situation, 
it seems, that locking problem start appearing, after more peers start
using tls transport
my tls only peers are: asterisk trunk, asterisk beta2 and eyebeam
sofphone
+several udp clients.



====================================================================== 

---------------------------------------------------------------------- 
 jamesgolovich - 02-17-08 23:46  
---------------------------------------------------------------------- 
I've uploaded bug11972-4.diff.txt, which is identical to the -3 patch
except it removes the code that makes do_monitor remove the dialogs.  Which
should definitely lead to some leaked memory but I'd like to make sure its
not this code causing your crashes.  

Your gdb2.txt looks like its related to this, but gdb.txt and gdb3.txt
look to be related to session timers.  I'll have to dig into session timers
more to see how those are handled or find someone else with more knowledge
about it to look at those 2 dumps. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-17-08 23:46  jamesgolovich  Note Added: 0082454                          
======================================================================