[asterisk-bugs] [Asterisk 0014464]: lock during simple call processing

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Apr 10 07:35:47 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14464 
====================================================================== 
Reported By:                pj
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14464
Category:                   Channels/chan_sip/General
Reproducibility:            unable to reproduce
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 171528 
Request Review:              
====================================================================== 
Date Submitted:             2009-02-12 06:27 CST
Last Modified:              2009-04-10 07:35 CDT
====================================================================== 
Summary:                    lock during simple call processing
Description: 
During normal operation, pure sip-sip calls, without special features (eg.
transfer), asterisk locks. Asterisk server had very small utilization -
three concurrent sip calls at maximum. After this lockout, all peers
becomed unreachable and asterisk must be manually restarted. CLI was not
locked.
"core show locks" attached

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

---------------------------------------------------------------------- 
 (0103070) pj (reporter) - 2009-04-10 07:35
 http://bugs.digium.com/view.php?id=14464#c103070 
---------------------------------------------------------------------- 
Do you have sufficient information to find source of this crash yet? I
posted gdb, that you require in the past. 
If you can't find where problem is, according to supplied debugs, you can
close this bugreport, because I can't supply better outputs, like valgrind,
because I don't know, how to invoke this lock. And also can't run from
valgrind all the time, for eg. until another lock appears again. thanks for
understanding! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-10 07:35 pj             Note Added: 0103070                          
======================================================================




More information about the asterisk-bugs mailing list