[asterisk-bugs] [JIRA] (ASTERISK-29296) stasis.c: FRACK!, Failed assertion bad magic number 0x0 for object

[Kevin Harwell (JIRA)]

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

Kevin Harwell commented on ASTERISK-29296:
------------------------------------------

When you run the {{ast_coredumper}} script [[1|https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-ast_coredumper]] it'll output several files. For example:
{noformat}
Processing core
Creating core-thread1.txt
Creating core-brief.txt
Creating core-info.txt
Creating core-full.txt
Creating core-locks.txt
{noformat}
These *.txt files should be small enough to attach to this issue. For now those files should be sufficient unless further indicated.

> stasis.c: FRACK!, Failed assertion bad magic number 0x0 for object
> ------------------------------------------------------------------
>
>                 Key: ASTERISK-29296
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29296
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_stasis
>    Affects Versions: 18.2.0, 18.4.0
>         Environment: Ubuntu 18
>            Reporter: BJ Weschke
>         Attachments: asterisk-frack.log.bz2
>
>
> Upon trying to add a channel to a bridge while testing Asterisk 18.2 in our QA environment, we started seeing these messages (see in attached log beginning at 14:09:42) in the full log, and after that point, anything related to the channel or the bridge in question seems to stream these errors into the log. The testers than gracefully shut down the Asterisk instance to clear the issue. We've not been able to reproduce this by doing the same use case that caused the issue in the first place. 



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