[asterisk-bugs] [JIRA] (ASTERISK-28021) backtrace.c: New crash due to double-free.

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-28021:
--------------------------------------------

Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected and the location of documentation that led you to that expectation.
3. The behavior you actually encountered.

To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

[2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

Your backtrace files are showing 30 threads hitting an assertion and getting an inline backtrace at the same time when the system crashed.  All of these threads were referencing freed memory because the ao2 object magic number is the MALLOC_DEBUG 0xdeaddead fill pattern.

> backtrace.c: New crash due to double-free.
> ------------------------------------------
>
>                 Key: ASTERISK-28021
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28021
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Logging
>    Affects Versions: 13.22.0
>         Environment: Linux version 3.10.0-693.2.2.el7.x86_64 (builder at kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP Tue Sep 12 22:26:13 UTC 2017
>            Reporter: Cirillo
>         Attachments: core.ANTIBES-2018-08-22T12-45-00-0300-brief.txt, core.ANTIBES-2018-08-22T12-45-00-0300-full.txt, core.ANTIBES-2018-08-22T12-45-00-0300-locks.txt, core.ANTIBES-2018-08-22T12-45-00-0300-thread1.txt
>
>
> Apparently the crash reported in ASTERISK-27340 doesn't went fixed.



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