[asterisk-bugs] [Asterisk 0013219]: possible missing unlock
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Dec 16 15:38:25 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13219
======================================================================
Reported By: pj
Assigned To: russell
======================================================================
Project: Asterisk
Issue ID: 13219
Category: Channels/chan_h323
Reproducibility: sometimes
Severity: minor
Priority: normal
Status: assigned
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 134005
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-08-01 07:50 CDT
Last Modified: 2008-12-16 15:38 CST
======================================================================
Summary: possible missing unlock
Description:
looking into asterisk cli, sometimes appears error after call hangup, that
channel lock still exist...
-- H323/ccm-gw-52 answered SIP/bill-gw-082fbb58
== Spawn extension (from-ipbx, 238, 2) exited non-zero on
'SIP/bill-gw-082fbb58'
[Aug 1 14:09:17] ERROR[16879]: utils.c:585 lock_info_destroy: Thread
'(null)' still has a lock! - '(channel lock)' (0x830bd30) from
'update_state' in chan_h323.c:1170!
======================================================================
----------------------------------------------------------------------
(0096494) svnbot (reporter) - 2008-12-16 15:38
http://bugs.digium.com/view.php?id=13219#c96494
----------------------------------------------------------------------
Repository: asterisk
Revision: 164881
U branches/1.4/main/utils.c
------------------------------------------------------------------------
r164881 | russell | 2008-12-16 15:38:24 -0600 (Tue, 16 Dec 2008) | 9 lines
Fix an issue where DEBUG_THREADS may erroneously report that a thread
is exiting while holding a lock.
If the last lock attempt was a trylock, and it failed, it will still be in
the
list of locks so that it can be reported.
(closes issue http://bugs.digium.com/view.php?id=13219)
Reported by: pj
------------------------------------------------------------------------
http://svn.digium.com/view/asterisk?view=rev&revision=164881
Issue History
Date Modified Username Field Change
======================================================================
2008-12-16 15:38 svnbot Checkin
2008-12-16 15:38 svnbot Note Added: 0096494
======================================================================
More information about the asterisk-bugs
mailing list