[asterisk-bugs] [JIRA] (ASTERISK-27617) Frack (crash), excessive refcount during Jitterbuffer operation
George Joseph (JIRA)
noreply at issues.asterisk.org
Wed Jan 24 11:10:49 CST 2018
[ https://issues.asterisk.org/jira/browse/ASTERISK-27617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
George Joseph updated ASTERISK-27617:
-------------------------------------
Assignee: Colin (was: Unassigned)
Status: Waiting for Feedback (was: Triage)
It looks like ASTERISK-27340, ASTERISK-27238, or ASTERISK-27412 may be root causes of your issue and they were all fixed in 13.19 and 15.2. Since 14.x is no longer receiving non-security fixes you'd have to use one of the 2 supported versions to get the fixes.
> Frack (crash), excessive refcount during Jitterbuffer operation
> ---------------------------------------------------------------
>
> Key: ASTERISK-27617
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-27617
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/Jitterbuffer
> Affects Versions: 14.6.0
> Environment: Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-109-generic x86_64)
>
> Reporter: Colin
> Assignee: Colin
> Labels: pjsip
> Attachments: CoreDump-brief.txt, CoreDump-full.txt, CoreDump-thread1.txt, jitterbuffer frack.txt
>
>
> During an __ast_read operation on a pushed frame (in abstract_jb::hook_event_cb()), the reference count on the ast_frame_subclass resulted in a FRACK, and system crash.
> The referenced field which triggered the failed assert was out->subclass.format - a reference to the Asterisk media format. Bumping this causes the EXCESSIVE_REF_COUNT to be exceeded.
> This instance of Asterisk was participating in a Stasis application, with around 28 callers. At the time of the crash around 20 were muted, but no bridge or channel operations were being carried out by the Stasis application.
> Core dump included as text file.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list