[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:              03-08-2008 12:11 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.



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

---------------------------------------------------------------------- 
 russell - 03-08-08 12:11  
---------------------------------------------------------------------- 
It has some of the things in the patch.  There were some deadlock avoidance
pieces that I have not merged yet, because I don't yet understand why they
are required.  Perhaps the reasoning is in some old debug attached here ...
I'll go looking later.

The biggest thing that the branch has, that the patch does not, is an
attempt to fix a memory leak that occurs on every TCP or TLS session.  The
"server_instance" struct gets stored in various places, and it's tricky to
figure out the right time to free it.

So, if you can make the branch crash, then it probably means that I still
don't have the logic right for when to free the memory, and I need to fix
it.  If it locks up, then I would like to see the locks output so I can
understand the deadlocks we are facing in this code. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-08-08 12:11  russell        Note Added: 0083643                          
======================================================================