[asterisk-bugs] [JIRA] (ASTERISK-27617) Frack (crash), excessive refcount during Jitterbuffer operation

Colin (JIRA) noreply at issues.asterisk.org
Fri Jan 26 05:48:49 CST 2018


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

Colin commented on ASTERISK-27617:
----------------------------------

Upgrade done. If you can suggest any test that we might do to check that our issue is fixed, please let me know.

> 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: Unassigned
>              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