|
|
Created:
4 years, 10 months ago by sandersd (OOO until July 31) Modified:
4 years, 10 months ago CC:
chromium-reviews, darin-cc_chromium.org, feature-media-reviews_chromium.org, jam, mcasas+watch_chromium.org, piman+watch_chromium.org, posciak+watch_chromium.org Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionDrop frames until first IDR in VTVDA.
This allows us to decode streams that incorrectly mark every frame
as a keyframe; we will drop frames until the first IDR and configure the
decoder then.
When this happens we log an error; it will show up in chrome://gpu (and
stderr).
This does mean that we are delaying decode failure (possibly indefinitely)
in that case.
BUG=229412, 583638, 583698, 516039
Committed: https://crrev.com/8a2f5658c6301691342e302ea618c61cad5d220c
Cr-Commit-Position: refs/heads/master@{#373964}
Patch Set 1 #
Total comments: 2
Patch Set 2 : Reduce spam. #
Total comments: 2
Messages
Total messages: 28 (13 generated)
The CQ bit was checked by sandersd@chromium.org to run a CQ dry run
sandersd@chromium.org changed reviewers: + dalecurtis@chromium.org, wolenetz@chromium.org
Description was changed from ========== Drop frames until first IDR in VTVDA. This allows us to decode streams that are incorrectly mark every frame as a keyframe; we will drop frames until the first IDR and configure the decoder then. This does mean that we are delaying decode failure possible indefinitely in that case. BUG=229412 ========== to ========== Drop frames until first IDR in VTVDA. This allows us to decode streams that are incorrectly mark every frame as a keyframe; we will drop frames until the first IDR and configure the decoder then. When this happens we log an error; it will show up in chrome://gpu (and stderr). This does mean that we are delaying decode failure possible indefinitely in that case. BUG=229412 ==========
Description was changed from ========== Drop frames until first IDR in VTVDA. This allows us to decode streams that are incorrectly mark every frame as a keyframe; we will drop frames until the first IDR and configure the decoder then. When this happens we log an error; it will show up in chrome://gpu (and stderr). This does mean that we are delaying decode failure possible indefinitely in that case. BUG=229412 ========== to ========== Drop frames until first IDR in VTVDA. This allows us to decode streams that incorrectly mark every frame as a keyframe; we will drop frames until the first IDR and configure the decoder then. When this happens we log an error; it will show up in chrome://gpu (and stderr). This does mean that we are delaying decode failure possible indefinitely in that case. BUG=229412 ==========
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1679503002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1679503002/1
Description was changed from ========== Drop frames until first IDR in VTVDA. This allows us to decode streams that incorrectly mark every frame as a keyframe; we will drop frames until the first IDR and configure the decoder then. When this happens we log an error; it will show up in chrome://gpu (and stderr). This does mean that we are delaying decode failure possible indefinitely in that case. BUG=229412 ========== to ========== Drop frames until first IDR in VTVDA. This allows us to decode streams that incorrectly mark every frame as a keyframe; we will drop frames until the first IDR and configure the decoder then. When this happens we log an error; it will show up in chrome://gpu (and stderr). This does mean that we are delaying decode failure (possibly indefinitely) in that case. BUG=229412 ==========
https://codereview.chromium.org/1679503002/diff/1/content/common/gpu/media/vt... File content/common/gpu/media/vt_video_decode_accelerator_mac.cc (right): https://codereview.chromium.org/1679503002/diff/1/content/common/gpu/media/vt... content/common/gpu/media/vt_video_decode_accelerator_mac.cc:649: LOG(ERROR) << "Illegal attempt to decode without IDR. Dropping frame."; DLOG(). Don't want to spam console on bad streams. Notably, these dropped frames won't be counted, which is unfortunate, but arguable depending on what you want to define a frame as :)
LGTM % : * --log spam per dalecurtis@ * in description (ideally in BUG= line), reference also the known bugs (for the bad streams) that this CL fixes.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
Description was changed from ========== Drop frames until first IDR in VTVDA. This allows us to decode streams that incorrectly mark every frame as a keyframe; we will drop frames until the first IDR and configure the decoder then. When this happens we log an error; it will show up in chrome://gpu (and stderr). This does mean that we are delaying decode failure (possibly indefinitely) in that case. BUG=229412 ========== to ========== Drop frames until first IDR in VTVDA. This allows us to decode streams that incorrectly mark every frame as a keyframe; we will drop frames until the first IDR and configure the decoder then. When this happens we log an error; it will show up in chrome://gpu (and stderr). This does mean that we are delaying decode failure (possibly indefinitely) in that case. BUG=229412,583638,583698,516039 ==========
https://codereview.chromium.org/1679503002/diff/1/content/common/gpu/media/vt... File content/common/gpu/media/vt_video_decode_accelerator_mac.cc (right): https://codereview.chromium.org/1679503002/diff/1/content/common/gpu/media/vt... content/common/gpu/media/vt_video_decode_accelerator_mac.cc:649: LOG(ERROR) << "Illegal attempt to decode without IDR. Dropping frame."; On 2016/02/05 22:35:27, DaleCurtis wrote: > DLOG(). Don't want to spam console on bad streams. > > Notably, these dropped frames won't be counted, which is unfortunate, but > arguable depending on what you want to define a frame as :) I've changed it to be limited to once per VTVDA instance. PTAL.
The CQ bit was checked by sandersd@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1679503002/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1679503002/20001
lgtm2
lgtm https://codereview.chromium.org/1679503002/diff/20001/content/common/gpu/medi... File content/common/gpu/media/vt_video_decode_accelerator_mac.cc (right): https://codereview.chromium.org/1679503002/diff/20001/content/common/gpu/medi... content/common/gpu/media/vt_video_decode_accelerator_mac.cc:653: missing_idr_logged_ = true; Do you want to reset this to false after the first real IDR?
On 2016/02/05 23:50:08, DaleCurtis wrote: > lgtm > > https://codereview.chromium.org/1679503002/diff/20001/content/common/gpu/medi... > File content/common/gpu/media/vt_video_decode_accelerator_mac.cc (right): > > https://codereview.chromium.org/1679503002/diff/20001/content/common/gpu/medi... > content/common/gpu/media/vt_video_decode_accelerator_mac.cc:653: > missing_idr_logged_ = true; > Do you want to reset this to false after the first real IDR? Can session_ become unset after being set without decode error already occurring?
https://codereview.chromium.org/1679503002/diff/20001/content/common/gpu/medi... File content/common/gpu/media/vt_video_decode_accelerator_mac.cc (right): https://codereview.chromium.org/1679503002/diff/20001/content/common/gpu/medi... content/common/gpu/media/vt_video_decode_accelerator_mac.cc:653: missing_idr_logged_ = true; On 2016/02/05 23:50:08, DaleCurtis wrote: > Do you want to reset this to false after the first real IDR? We could do that, but I'm mostly just concerned with making sure there is a log message at all. One other option would be to switch from LOG to DLOG after the first message.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by sandersd@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from wolenetz@chromium.org Link to the patchset: https://codereview.chromium.org/1679503002/#ps20001 (title: "Reduce spam.")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1679503002/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1679503002/20001
Message was sent while issue was closed.
Description was changed from ========== Drop frames until first IDR in VTVDA. This allows us to decode streams that incorrectly mark every frame as a keyframe; we will drop frames until the first IDR and configure the decoder then. When this happens we log an error; it will show up in chrome://gpu (and stderr). This does mean that we are delaying decode failure (possibly indefinitely) in that case. BUG=229412,583638,583698,516039 ========== to ========== Drop frames until first IDR in VTVDA. This allows us to decode streams that incorrectly mark every frame as a keyframe; we will drop frames until the first IDR and configure the decoder then. When this happens we log an error; it will show up in chrome://gpu (and stderr). This does mean that we are delaying decode failure (possibly indefinitely) in that case. BUG=229412,583638,583698,516039 ==========
Message was sent while issue was closed.
Committed patchset #2 (id:20001)
Message was sent while issue was closed.
Description was changed from ========== Drop frames until first IDR in VTVDA. This allows us to decode streams that incorrectly mark every frame as a keyframe; we will drop frames until the first IDR and configure the decoder then. When this happens we log an error; it will show up in chrome://gpu (and stderr). This does mean that we are delaying decode failure (possibly indefinitely) in that case. BUG=229412,583638,583698,516039 ========== to ========== Drop frames until first IDR in VTVDA. This allows us to decode streams that incorrectly mark every frame as a keyframe; we will drop frames until the first IDR and configure the decoder then. When this happens we log an error; it will show up in chrome://gpu (and stderr). This does mean that we are delaying decode failure (possibly indefinitely) in that case. BUG=229412,583638,583698,516039 Committed: https://crrev.com/8a2f5658c6301691342e302ea618c61cad5d220c Cr-Commit-Position: refs/heads/master@{#373964} ==========
Message was sent while issue was closed.
Patchset 2 (id:??) landed as https://crrev.com/8a2f5658c6301691342e302ea618c61cad5d220c Cr-Commit-Position: refs/heads/master@{#373964} |