[asterisk-bugs] [JIRA] (ASTERISK-27862) ARI: Crashing on json_mem_free (after sending event)

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-27862:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> ARI: Crashing on json_mem_free (after sending event)
> ----------------------------------------------------
>
>                 Key: ASTERISK-27862
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27862
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_stasis
>    Affects Versions: 13.21.0
>            Reporter: Stefan Repke
>
> ARI is activated and there are several apps connected with "subscribeAll=true".
> Then, Asterisk crashes occasionally when delivering ARI events!
> With normal workload, this happens once or twice a day. It can be provoked by adding many (eg. 10) ARI subscribers and producing lots of events (eg. PeerStatusChange by registering/unregistering a peer).
> I coredumped three crashes, all having a memory corruption in {{json_mem_free}} at {{json.c:84}}; cf. attached backtraces.
> * Backtrace 2 and 3 have similar problems: {{double free or corruption (fasttop)}},
> * Backtrace 1 looks like wrong memory access.
> I've also attached the last logger messages from the CLI (debug=5 / verbose=5).



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