[asterisk-bugs] [Asterisk 0016967]: Nested Dial()s that use U() or M() results in: '&(audiohook)->lock' freed more times than we've locked!

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16967 
====================================================================== 
Reported By:                DennisD
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16967
Category:                   Core/General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     closed
Asterisk Version:           SVN 
JIRA:                       SWP-1041 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 unable to reproduce
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-03-04 21:11 CST
Last Modified:              2010-06-08 10:11 CDT
====================================================================== 
Summary:                    Nested Dial()s that use U() or M() results in: 
'&(audiohook)->lock' freed more times than we've locked!
Description: 
/include/asterisk/lock.h: audiohook.c line 648
(audio_audiohook_write_list): Error obtaining mutex: Invalid argument
/include/asterisk/lock.h: audiohook.c line 662
(audio_audiohook_write_list): mutex '&(audiohook)->lock' freed more times
than we've locked!
/include/asterisk/lock.h: audiohook.c line 662
(audio_audiohook_write_list): Error releasing mutex: Invalid argument

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

---------------------------------------------------------------------- 
 (0123116) lmadsen (administrator) - 2010-06-08 10:11
 https://issues.asterisk.org/view.php?id=16967#c123116 
---------------------------------------------------------------------- 
I agree that res_timing_timerfd has some issues odd like this, as does
res_timing_pthread.

Unfortunately unless we can reproduce these consistently we won't be able
to move them forward.

But as you stated, moving to dahdi_dummy seems to resolve the issue, so if
you're able to reproduce the issues you're having with res_timing_timerfd
in the future, please do open another issue so we can try to catch and
resolve those issues.

Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-08 10:11 lmadsen        Note Added: 0123116                          
2010-06-08 10:11 lmadsen        Status                   acknowledged => closed
2010-06-08 10:11 lmadsen        Resolution               open => unable to
reproduce
======================================================================