[Home]

Summary:ASTERISK-15601: astobj2.c:279
Reporter:Ignacio Cisternas (cotocisternas)Labels:
Date Opened:2010-02-10 07:46:39.000-0600Date Closed:2011-06-07 14:00:44
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) backtrace.txt
Description:I don't know why, but with no reason i get this error, an Asterisk go crash.

astobj2.c:279 internal_ao2_ref: refcount -1 on object 0x8e9d9a8

I look for the line 279 in main/astobj2.c and i see this.

/* this case must never happend */ ??... well.. some time happen's.

277         /* this case must never happen */
278         if (current_value < 0)
279                 ast_log(LOG_ERROR, "refcount %d on object %p\n", current_value, user_data);
280
281         if (current_value <= 0) { /* last reference, destroy the object */
282                 if (obj->priv_data.destructor_fn != NULL) {
283                         obj->priv_data.destructor_fn(user_data);
284                 }

Dont have any idea wat is this, only know this crash my asterisk.



****** ADDITIONAL INFORMATION ******

[LOG for that moment]

[2010-02-10 09:52:18] WARNING[5231] pbx_config.c: Can't use 'next' priority on the first entry!
[2010-02-10 09:52:32] WARNING[5229] app_voicemail.c: IMAP Warning: SECURITY PROBLEM: insecure server advertised AUTH=PLAIN
[2010-02-10 09:52:33] ERROR[5229] app_voicemail.c: IMAP Error: Quota not available on this IMAP server
[2010-02-10 09:53:22] ERROR[5229] astobj2.c: refcount -1 on object 0x8e9d9a8
Comments:By: Ignacio Cisternas (cotocisternas) 2010-02-10 08:43:57.000-0600

Right now, i have another crash for this error, i dont know if have somethin in common:

 -- SIP/IFX2-00000090 is making progress passing it to SIP/1003-0000008e
 == Extension Changed 1003 new state Idle for Notify User 1001
 == Spawn extension (ldn, 9782662, 2) exited non-zero on 'SIP/1003-0000008e'
 == Extension Changed 1003 new state Idle for Notify User 1203
 == Extension Changed 1003 new state Idle for Notify User 1204
[2010-02-10 11:41:16] ERROR[5923]: astobj2.c:116 INTERNAL_OBJ: bad magic number 0x3a39333a for 0x8f0f898

By: Ignacio Cisternas (cotocisternas) 2010-02-10 13:25:48.000-0600

Another crash:

[2010-02-10 16:22:18] ERROR[7437]: astobj2.c:116 INTERNAL_OBJ: bad magic number 0x3a31323a for 0xa208398

By: Leif Madsen (lmadsen) 2010-02-10 15:16:38.000-0600

Per the bug guidelines, you need to provide a console trace with 'core set verbose 10' and 'core set debug 10' with debug logging levels enabled in logger.conf.

In addition, you need to provide a backtrace file per the doc/backtrace.txt documentation in your Asterisk source. Please attach the backtrace as a text file to this issue, and not as a comment.

By: Ignacio Cisternas (cotocisternas) 2010-02-10 15:27:31.000-0600

I have verbose in 30, but few days ago i turn in off, debug... i put it in 10 again, and hoping crash again to see what is happending...

Sorry for my bad english.

Ty all.

By: Ignacio Cisternas (cotocisternas) 2010-02-11 07:45:51.000-0600

Ok, lets here other crash, with Verbose 10 and Debug 10

[2010-02-11 09:38:31] ERROR[8309] chan_sip.c: Peer '99904' is trying to register, but not configured as host=dynamic
[2010-02-11 09:38:31] NOTICE[8309] chan_sip.c: Registration from '<sip:99904@192.168.1.201>' failed for '192.168.1.203' - Peer is not supposed to register
[2010-02-11 09:56:30] NOTICE[8309] chan_sip.c: Peer '1203' is now Reachable. (165ms / 2000ms)
[2010-02-11 09:56:41] ERROR[8309] astobj2.c: bad magic number 0x4953006c for 0x9d4d500
[2010-02-11 09:57:10] NOTICE[12682] cdr.c: CDR simple logging enabled.
[2010-02-11 09:57:10] NOTICE[12682] loader.c: 200 modules will be loaded.

By: Leif Madsen (lmadsen) 2010-02-22 15:51:40.000-0600

Heh, you uploaded the backtrace.txt file -- I'm looking for you to follow the instructions in that file and upload your own backtrace from the core file.

By: Leif Madsen (lmadsen) 2010-03-17 08:34:25

Suspended due to lack of response from the reporter.

By: Martin Lujan (mlujan) 2020-11-16 12:25:49.137-0600

is this resolved? Because to date it happens in Asterisk 1.8. Someone confirm me if in later versions it is solved?