Summary:	ASTERISK-12503: possible missing unlock
Reporter:	pj (pj)	Labels:
Date Opened:	2008-08-01 07:50:26	Date Closed:	2008-12-16 15:38:25.000-0600
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_h323
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
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!
Comments:	By: Jason Parker (jparker) 2008-08-13 15:54:13 Looking at the code path, and the update_state function, I don't see how this could be happening. It may be related to a bug that was fixed regarding channel locks.  Is this still happening? By: pj (pj) 2008-08-14 15:15:57 yes, it still happen in my setup, seems, that only sip to h323 direction is affected (oposite is OK), error message appears after call hangup... I have Asterisk SVN-trunk-r136787, should I try fresh svn checkout? [Aug 13 13:16:42]     -- H323/ccm-gw-70 answered SIP/bill-gw-082d7598 [Aug 13 13:18:04]   == Spawn extension (from-ipbx, 510, 2) exited non-zero on 'SIP/bill-gw-082d7598' [Aug 13 13:18:04] ERROR[26196]: utils.c:585 lock_info_destroy: Thread '(null)' still has a lock! - '(channel lock)' (0x82ecb78) from 'update_state' in chan_h323.c:1170! [Aug 13 13:18:35]     -- SIP/ipbx-gw-082eaff0 is ringing [Aug 13 13:19:08] ERROR[26205]: utils.c:585 lock_info_destroy: Thread '(null)' still has a lock! - '(channel lock)' (0x82dd2f0) from 'hangup_connection' in chan_h323.c:2406! [Aug 13 13:19:08]   == Spawn extension (from-ccm, *628, 2) exited non-zero on 'H323/ip$192.168.40.7:49878/1067' By: Jeff Peeler (jpeeler) 2008-12-16 14:38:40.000-0600 I haven't been able to reproduce this. Did the problem occur simply after making a SIP to H323 call and then hanging up? By: Digium Subversion (svnbot) 2008-12-16 15:38:25.000-0600 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 ASTERISK-12503) Reported by: pj ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=164881