[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]

A NOTE has been added to this issue. 
====================================================================== 
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:                     acknowledged
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:              
====================================================================== 
Date Submitted:             2010-03-04 21:11 CST
Last Modified:              2010-04-29 07:09 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

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

---------------------------------------------------------------------- 
 (0121150) Jiri Uncovsky (reporter) - 2010-04-29 07:09
 https://issues.asterisk.org/view.php?id=16967#c121150 
---------------------------------------------------------------------- 
Hello, I also met this bug on CentOS 5.4/x86_64 with Asterisk 1.6.1.18. I
can reproduce it simply by running Asterisk on the machine again but I
don't know what steps are required to reproduce it on demand.

If there is any way I can help with resolution of this bug, please let me
know.

Just a speculation: I am unable to reproduce the bug on other machines.
Unlike the other Asterisks, the Asterisk that exhibits the bug is
configured to communicate via two network interfaces - one interface is a
SIP trunk to the outer world, the other interface is for local telephone
network.

Stack trace after the crash is attached. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-29 07:09 Jiri Uncovsky  Note Added: 0121150                          
======================================================================