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

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-27617:
------------------------------------------

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].

> 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
>
> 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 message was sent by Atlassian JIRA
(v6.2#6252)