1370079 - VP9 hardware decoding is disabled when e10s is enabled

Status: RESOLVED FIXED

(Core :: Audio/Video: Playback, defect)

Description

[Jean-Yves Avenard [:jya]]

The logic introduced in bug 1338011 is flawed.

We only enable VP9 hardware decoding when we know the platform have DXVA enabled.
The WMF PDM is queried to find out if it supports VP9 in the content process.

But in the content process, dxva is now always disabled whenever we have a GPU process.

as a result, we never have VP9 hardware decoding if e10s and GPU decoding is enabled.

Comment 1

[Jean-Yves Avenard [:jya]]

Attachment: Bug 1370079: P1. Don't check for DXVA support when checking for VP9 support.

SupportsMimeType is called in the content process, for which, following bug  1338011, dxva is marked as disabled.

CanCreateWMFDecoder already performs the check of allowing VP9 only if it's hardware accelerated, so we don't need to test if dxva is enabled prior.

Review commit: https://reviewboard.mozilla.org/r/147154/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/147154/

Comment 2

[Jean-Yves Avenard [:jya]]

[Tracking Requested - why for this release]:

Comment 3

[Matt Woodrow (:mattwoodrow)]

Comment on attachment 8875729 [details]
Bug 1370079: P1. Don't check for DXVA support when checking for VP9 support.

https://reviewboard.mozilla.org/r/147154/#review151556

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/cc4812a78c23
P1. Don't check for DXVA support when checking for VP9 support. r=mattwoodrow

Comment 5

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/cc4812a78c23