Summary:ASTERISK-16084: Asterisk crash after Hangup app
Reporter:Andrey Solovyev (corruptor)Labels:
Date Opened:2010-05-12 07:46:00Date Closed:2010-05-17 11:28:08
Versions:Frequency of
Environment:Attachments:( 0) bt.txt
Description:This is probably related to astobj issue 0017321
To reproduce create simple context.

[testcon]                                                                       exten => _1X.,1,Noop()                
exten => _1X.,n,Hangup

-- Executing [111@testcon:1] NoOp("SIP/1102-00000000", "") in new stack
-- Executing [111@testcon:2] Hangup("SIP/1102-00000000", "") in new stack                                                      
 == Spawn extension (testcon, 111, 2) exited non-zero on 'SIP/1102-00000000'
[May 12 16:20:59] ERROR[5000]: /usr/src/asterisk- __ast_pthread_mutex_destroy: astobj2.c line 268 (ao2_ref): Error destroying mutex &obj->priv_data.lock: Device or resource busy
[May 12 16:20:59] ERROR[5000]: astobj2.c:115 INTERNAL_OBJ: bad magic number 0x2e303132 for 0x8a145d0                                
[May 12 16:20:59] ERROR[5000]: utils.c:523 lock_info_destroy: Thread 'pbx_thread           started at [ 3993] pbx.c ast_pbx_start()' still has a lock! - 'p' (0x8a145d0) from 'sip_hangup' in chan_sip.c:5152!

Then crash. Backtrace is attached.
Comments:By: Paul Belanger (pabelanger) 2010-05-12 08:25:43

Can't open your backtrace, can you attach another.  Confirm you can view it once attached.

By: Andrey Solovyev (corruptor) 2010-05-12 08:58:12

I've just tried to download on two PCs (one Linux with KWrite and Win with notepad) and I see the backtrace.
It's just text file with full gdb output with bt full and threads apply all bt in it.

By: Leif Madsen (lmadsen) 2010-05-13 09:22:21

Can you also reproduce this on the latest 1.6.2 release?


Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.6.0 and 1.6.1 branches has ended. For continued maintenance support please move to the 1.6.2 branch.

More information on this change can be found in the release announcement: http://www.asterisk.org/node/49924

By: Andrey Solovyev (corruptor) 2010-05-14 02:19:04 works ok.
It seems that I have to move to 1.6.2 branch :).

By: Leif Madsen (lmadsen) 2010-05-17 11:28:07

Fixed in per reporter.