[asterisk-bugs] [JIRA] (ASTERISK-26725) astobj2.c: FRACK!, Failed assertion bad magic number

[Richard Mudgett (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234691#comment-234691 ] 

Richard Mudgett commented on ASTERISK-26725:
--------------------------------------------

These assertion backtraces are not that useful.  They can only say that a task processor job/task somewhere in res_pjsip was trying to lock a destroyed ao2 object.  Enabling BETTER_BACKTRACES and DONT_OPTIMIZE would provide more information in those assertion backtraces.

Since this is dealing with a destroyed ao2 object, turning on MALLOC_DEBUG will likely provide even better information from a segfault when it tries to use the destroyed object.

> astobj2.c: FRACK!, Failed assertion bad magic number
> ----------------------------------------------------
>
>                 Key: ASTERISK-26725
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26725
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 13.13.1
>            Reporter: Dmitriy Serov
>            Assignee: Unassigned
>         Attachments: assertions-1.txt, assertions-2.txt, syslog.txt
>
>
> Installing asterisk 13.13.1 on ubuntu server with bundled pjproject.
> Asterisk segfaults a lot of time (attachment syslog.txt)
> Two attachemts with assertion logs.
> I beg you at least to tell workarounds ASAP.



--
This message was sent by Atlassian JIRA
(v6.2#6252)