VP9 hardware decoding is disabled when e10s is enabled

RESOLVED FIXED in Firefox 55

Status

()

defect
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: jya, Assigned: jya)

Tracking

({regression})

unspecified
mozilla55
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox-esr52 unaffected, firefox54 unaffected, firefox55+ fixed)

Details

Attachments

(1 attachment)

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.
Assignee: nobody → jyavenard
[Tracking Requested - why for this release]:
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
Attachment #8875729 - Flags: review?(matt.woodrow) → review+
Pushed by jyavenard@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/cc4812a78c23
P1. Don't check for DXVA support when checking for VP9 support. r=mattwoodrow
https://hg.mozilla.org/mozilla-central/rev/cc4812a78c23
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in before you can comment on or make changes to this bug.