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

Richard Mudgett (JIRA) noreply at issues.asterisk.org
Tue May 22 18:04:55 CDT 2018


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

Richard Mudgett commented on ASTERISK-27862:
--------------------------------------------

Which version of libjansson are you using?  A change was made https://gerrit.asterisk.org/#/c/8186/ that removed some locking to take advantage of some thread safe changes done in libjansson version 2.11.

> 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
>            Assignee: Stefan Repke
>         Attachments: backtrace 1.txt, backtrace 2.txt, backtrace 3.txt, cli.txt
>
>
> 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)



More information about the asterisk-bugs mailing list