[asterisk-bugs] [JIRA] (ASTERISK-28237) "FRACK!, Failed assertion bad magic number" happens when unsubscribe an application from an event source

[Evgenios Muratidis (JIRA)]

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

Evgenios Muratidis commented on ASTERISK-28237:
-----------------------------------------------

Hi George! Could you, please, lookup at Gerrit reviews of this issue. I think the current reviewer cannot understand with my suggested changes, with applied patch. Please, help!

> "FRACK!, Failed assertion bad magic number" happens when unsubscribe an application from an event source
> --------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28237
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28237
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Stasis
>    Affects Versions: 13.18.0, 16.1.1
>            Reporter: Lucas Tardioli Silveira
>            Assignee: Unassigned
>              Labels: pjsip
>         Attachments: ari.conf, ari-test2, core-brief.txt, core-full.txt, debug_frack1
>
>
> I'm facing this issue when I try to unsubscribe an application.
> Scenario:
> I have multiple applications connecting to my Asterisk server.
> All the time that my application connects to Asterisk I send a subscribe message like:
> POST /ari/applications/my-app1/subscription?eventSource=endpoint:PJSIP
> (for the other applications I can have my-app2, my-app3 and so on...)
> And when I disconnect to Asterisk I send:
> DELETE /ari/applications/my-app1/subscription?eventSource=endpoint:PJSIP
> The problem happens when I have at least two applications running and one of them needs to disconnect. So, at the moment that I send the message to unsubscribe the "FRACK" happens.
> That was happening on asterisk 13.18-cert2 then I updated it to the lastest version, 16.1.1 but it is still happening.



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