Summary:	ASTERISK-22513: astobj2.c INTERNAL_OBJ: bad magic number for 0x7f0b500174e8. Object is likely destroyed
Reporter:	Gopalakrishnan N (saigop)	Labels:
Date Opened:	2013-09-12 11:34:53	Date Closed:	2013-09-26 13:27:12
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Channels/chan_sip/General
Versions:	11.1.2	Frequency of Occurrence	Occasional
Related Issues:
Environment:	Cent OS 6.4 (64bit) Sangoma W400 GSM Card	Attachments:	( 0) backtrace1.txt
Description:	Trying to call via GSM Card, while in ringback tone if i disconnect from Asterisk side (hangup from softphone/hardphone) the following error occurs, {noformat} [Sep 13 08:25:20] ERROR[31626]: astobj2.c:155 INTERNAL_OBJ: bad magic number for 0x7f0b500174e8. Object is likely destroyed. {noformat} At some times, Asterisk restarts automatically, not repetitive.
Comments:	By: Rusty Newton (rnewton) 2013-09-12 16:45:00.204-0500 You haven't provided enough information for us to look into this issue. Please read through the issue tracker guidelines: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines 1. Please test with the latest version of the 11 branch to see if the issue has already been resolved. If not, then please follow the next steps. 2. bq. At some times, Asterisk restarts automatically, not repetitive. Sounds like Asterisk is crashing. Please follow [the instructions located on the wiki|https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace] and attach the resulting backtrace to this issue. 3. bq. [Sep 13 08:25:20] ERROR[31626]: astobj2.c:155 INTERNAL_OBJ: bad magic number for 0x7f0b500174e8. Object is likely destroyed. Additionally please follow the [reference count debugging guide|https://wiki.asterisk.org/wiki/display/AST/Reference+Count+Debugging] for chan_sip and attach the resulting file to this issue. 4. Please collect and post a [VERBOSE and DEBUG log|https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information] for the complete call so that we can see more detail as to what is happening. By: Richard Mudgett (rmudgett) 2013-09-26 11:40:46.654-0500 The attached backtrace is from an optimized build.  However, it is enough to show that the crash is happening as a result of the third party channel driver.  You should get support from the vendor of that channel driver. By: Gopalakrishnan N (saigop) 2013-09-26 12:18:43.441-0500 sorry for my late reply. attached is the backtrace file. And Asterisk version we are using 11.1.2. The log what we get from CLI is, - Span 4: Remote side ringing -- DAHDI/7-1 is ringing -- Nobody picked up in 30000 ms -- Span 4: Call Hung up -- Hungup 'DAHDI/7-1' -- Executing [091XXXXXXXX@call_outbound:5] Hangup("SIP/8001-0000000f", "") in new stack == Spawn extension (call_outbound, 091XXXXXXXX, 5) exited non-zero on 'SIP/8001-0000000f' == MixMonitor close filestream (mixed) == End MixMonitor Recording SIP/8001-0000000f -- Span 4: Call hangup requested [Sep 24 22:09:43] ERROR[25841]: astobj2.c:155 INTERNAL_OBJ: bad magic number for 0x7f6020010648. Object is likely destroyed. [Sep 24 22:09:43] ERROR[25841]: astobj2.c:155 INTERNAL_OBJ: bad magic number for 0x7f6020010648. Object is likely destroyed. [Sep 24 22:09:43] WARNING[25841]: channel.c:1332 __ast_queue_frame: Unable to write to alert pipe on (null) (qlen = 0): Bad file descriptor! [Sep 24 22:09:43] ERROR[25841]: astobj2.c:155 INTERNAL_OBJ: bad magic number for 0x7f6020010648. Object is likely destroyed. [Sep 24 22:09:43] ERROR[25841]: astobj2.c:155 INTERNAL_OBJ: bad magic number for 0x7f6020010648. Object is likely destroyed. [Sep 24 22:09:43] ERROR[25841]: astobj2.c:155 INTERNAL_OBJ: bad magic number for 0x7f6020010648. Object is likely destroyed. [Sep 24 22:09:43] ERROR[25841]: astobj2.c:155 INTERNAL_OBJ: bad magic number for 0x7f6020010648. Object is likely destroyed. -- Span 4: Call Release Thanks By: Gopalakrishnan N (saigop) 2013-09-26 12:21:28.254-0500 Ok thanks, let me contact the vendor. Thank you. By: Matt Jordan (mjordan) 2013-09-26 13:27:12.282-0500 Closing as "Not a Bug", as this is not a bug in a supported module.