New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 631841 link

Starred by 2 users
Status: Fixed
Owner:
█ jbau...@chromium.org
not on Chrome anymore
Closed: Jul 2016
Cc:
dalecur...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Renderer attempts to use hardware video decoder for VP9 on systems that don't support it.

Project Member Reported by jbau...@chromium.org, Jul 26 2016 
DXVAVideoDecodeAccelerator::GetSupportedProfiles returns VP8 and VP9 profiles even if VPx hardware decoding is disabled. That causes the renderer to attempt to attempt to create a hardware video decoder for those videos, which is inefficient.

Comment 1 by dalecur...@chromium.org, Jul 26 2016 

Thanks for filing, I forgot to make a bug for this.
Project Member

Comment 2 by bugdroid1@chromium.org, Jul 27 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3d65007a96c2b57a635401a6e5ba71b02083c536

commit 3d65007a96c2b57a635401a6e5ba71b02083c536
Author: jbauman <jbauman@chromium.org>
Date: Wed Jul 27 06:34:58 2016

Don't mark VP9 as supported for hardware decoding if it's blacklisted

This should avoid a renderer roundtrip when decoding videos on some
systems where hardware video decoding isn't supported.

BUG= 631841 

Review-Url: https://codereview.chromium.org/2187673003
Cr-Commit-Position: refs/heads/master@{#408059}

[modify] https://crrev.com/3d65007a96c2b57a635401a6e5ba71b02083c536/media/gpu/dxva_video_decode_accelerator_win.cc
[modify] https://crrev.com/3d65007a96c2b57a635401a6e5ba71b02083c536/media/gpu/dxva_video_decode_accelerator_win.h
[modify] https://crrev.com/3d65007a96c2b57a635401a6e5ba71b02083c536/media/gpu/gpu_video_decode_accelerator_factory.cc

Comment 3 by jbau...@chromium.org, Jul 28 2016

Status: Fixed (was: Started)
►

Sign in to add a comment