Handle incoming config changes during decoder fallback |
||||||
Issue descriptionIn decoder stream, the following scenario might happen when we support multiple decode requests. - Decoder is initialized successfully. - Request (#1) buffer from Demuxer. - OnBufferReady() is called back (#1) with kOk, send buffer to decoder, request buffer (#2) from demuxer. - OnDecodeDone() called back (#1) with a DecodeStatus::DECODE_ERROR, fallback to new decoder via DecoderSelector. - OnBufferReady() is called back (#2) with kConfigChanged. - OnDecoderSelected() is called back. In this case, the config with which the decoder was initialized might be stale, as it have been pulled from the stream before the kConfigChanged was signaled. The STATE_CONFIG_CHANGE_RECEIVED_WHILE_REINITIALIZING_DECODER was created in order to signal an error for this edge case. However, we could record the stream configs and play them back to the decoder. This would best be done when we refactor the decoder stream.
,
Apr 14 2016
,
Apr 17 2017
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 19 2017
,
Apr 20 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 20 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by sande...@chromium.org
, Apr 14 2016Labels: -Hotlist-VideoStack Hotlist-CodeHealth