Created attachment 8588932 [details] [diff] [review] blacklist-dxva-intel We seem to be getting a lot of reports of black video on youtube with intel GPU's and older drivers. We've confirmed locally that 184.108.40.2069 is broken, and 220.127.116.1122 works. We'll blacklist everything before 2622 since the most accurate data we have available currently.
Comment on attachment 8588932 [details] [diff] [review] blacklist-dxva-intel Review of attachment 8588932 [details] [diff] [review]: ----------------------------------------------------------------- ::: widget/windows/GfxInfo.cpp @@ +1103,5 @@ > > + APPEND_TO_DRIVER_BLOCKLIST2(DRIVER_OS_ALL, > + (nsAString&)GfxDriverInfo::GetDeviceVendor(VendorIntel), GfxDriverInfo::allDevices, > + nsIGfxInfo::FEATURE_HARDWARE_VIDEO_DECODING, nsIGfxInfo::FEATURE_BLOCKED_DRIVER_VERSION, > + DRIVER_LESS_THAN, V(8,15,10,22622)); s/22622/2622/
Comment on attachment 8588932 [details] [diff] [review] blacklist-dxva-intel Approval Request Comment [Feature/regressing bug #]: HTML5 Video [User impact if declined]: Black video on youtube when MSE gets enabled. [Describe test coverage new/current, TreeHerder]: Manually tested and confirmed that 2622 driver works. [Risks and why]: Low risk, just a blacklist change. [String/UUID change made/needed]: None
Comment on attachment 8588932 [details] [diff] [review] blacklist-dxva-intel Should be in 38 beta 3.
Ran afoul of bug 1149343. Backed out and re-landed with that fixed. https://hg.mozilla.org/releases/mozilla-aurora/rev/a8f5e241cb6f https://hg.mozilla.org/releases/mozilla-aurora/rev/7be40dfbc869
[Tracking Requested - why for this release]: If we release a 37.0.2 chemspill, we will want this GPU blocklist fix. We would no longer need hotfix bug 1152630.
Sylvestre, Lawrence said said a 37.0.2 release may go to build as early as April 14. I wanted to make sure we can get this GPU blocklist changes in 37.0.2 so we don't need the hotfix in bug 1152630.
Comment on attachment 8588932 [details] [diff] [review] blacklist-dxva-intel Sure. I guess Lawrence was going to approve it, so, I am approving it for you to make sure it lands soon.
I've tried to verify if blacklisting works through the aid of spoofing graphics data, on a Windows 7 x64 machine. I did not notice any change for the "media.windows-media-foundation.use-dxva" pref or the "GPU Accelerated Windows" value in about:support, when trying driver versions that should be blocked or unblocked. The actual steps to test this are below. Am I looking for the wrong things to verify here? Maybe this method of spoofing cannot be used to verify DXVA blocking? Steps to verify: 1. Firefox 37.0.2 is installed at some location. 2. Create "spoofed-firefox.bat" file with following content (pointing to location of Firefox 37.0.2): SET MOZ_GFX_SPOOF_WINDOWS_VERSION=60001 SET MOZ_GFX_SPOOF_VENDOR_ID=0x8086 SET MOZ_GFX_SPOOF_DEVICE_ID=0x8108 SET MOZ_GFX_SPOOF_DRIVER_VERSION=18.104.22.1682 "G:\Mozilla\37.0.2\firefox.exe" -p -no-remote 3. Open "spoofed-firefox.bat" to launch Firefox 37.0.2, create a new profile, start Firefox 37.0.2, and verify "about:support" and "about:config". I've used the method above to successfully verify blacklisting for other features like D2D, OMTC, WebGL.
Matt - Can you answer Florin's question in comment 13?
We don't report DXVA status in about:support, nor will the blacklist actually change the pref. I'm not sure how we can verify this without one of the affected machines (or by checking if DXVA is being used with a debugger). We should make sure we report DXVA status somewhere for the future.
(In reply to Matt Woodrow (:mattwoodrow) from comment #15) > We should make sure we report DXVA status somewhere for the future. Can you make sure you have a bug on file for this and put in your plans?
Bug 1151611 covers doing that.