[asterisk-bugs] [JIRA] (ASTERISK-25768) astobj2.c:124 INTERNAL_OBJ: bad magic number [..] for object [..]
Ronaldo Rathis Sacco (JIRA)
noreply at issues.asterisk.org
Wed Feb 10 06:56:32 CST 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-25768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ronaldo Rathis Sacco updated ASTERISK-25768:
--------------------------------------------
Attachment: backtrace.txt
backtrace file
> astobj2.c:124 INTERNAL_OBJ: bad magic number [..] for object [..]
> ------------------------------------------------------------------
>
> Key: ASTERISK-25768
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25768
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: . I did not set the category correctly.
> Affects Versions: 1.8.31.1, 1.8.32.3, 13.6.0
> Environment: Ubuntu 12.04 LTS
> model name : Intel(R) Celeron(R) CPU J1800 @ 2.41GHz
> MemTotal: 4016276 kB
> Asterisk 1.8.32.3
> Linux asterisk-prefeitura-npt 3.2.0-23-generic-pae #36-Ubuntu SMP Tue Apr 10 22:19:09 UTC 2012 i686 i686 i386 GNU/Linux
> Reporter: Ronaldo Rathis Sacco
> Severity: Critical
> Attachments: backtrace.txt
>
>
> Many message of "bad magic number" appears and after asterisk stops automatically (or restart if I use safe_asterisk). Last time, appeared more then 400 times (about 10 per second).
> The message is:
> [Feb 10 08:41:32] ERROR[29506] astobj2.c: bad magic number for object 0xb6e9a728. Object is likely destroyed.
> or, sometimes:
> [Feb 10 08:41:34] ERROR[29506] astobj2.c: bad magic number 0x4d584157 for object 0xb6e9a728
> I dont know exactly how to reproduce this error. But it happens ~5 times per week.
> I tried to change version, but same error happened.
> On that server have about 92 SIP peers and more 100 analogic peers (Khomp device).
> Attached are complete logs and gdb file.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list