Please copy/paste the results of about:gpu from your system.

hardware acceleration is checked in both Chrome and Chromium settings

Deleted: gpu_chrome.html 46.2 KB

gpu_chrome.html 46.2 KB View Download

Deleted: gpu_chromium.html 47.4 KB

gpu_chromium.html 47.4 KB View Download

No problem with Chromium 51.0.2683.0
https://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win_x64/381909/

Deleted: gpu_chromium51.html 149 KB

gpu_chromium51.html 149 KB View Download

Your machine has AMD switchable graphics and that's why ANGLE's Direct3D 11 backend is being forced off. You could try running Chrome from the Command Prompt with the command line argument --ignore-gpu-blacklist and see whether it gets farther. There are some other driver bug workarounds being applied there which you might need to use. From the command prompt something like this would be needed:

C:\Program Files (x86)\Google Chrome\Application\chrome.exe --ignore-gpu-blacklist --disable-accelerated-video-decode

Let us know if this makes both WebGL and YouTube videos work. We can consider revisiting these blacklist entries if so.

OK.
Webgl and YouTube work with --ignore-gpu-blacklist --disable-accelerated-video-decode and also with only --ignore-gpu-blacklist.

Hi, 

What is the next step ? 

John, could you re-test on a Windows machine with AMD switchable GPU and recent drivers, and take a guess as to whether the D3D11 code path could be enabled for this configuration?

Should we remove the blacklist entry and see whether crash rates go up on Canary?

D3D9 should still be working, right?

Presumably it should be; another question is why ANGLE's D3D9 backend fails to initialize (for WebGL, at least) on this hardware.

--use-angle d3d11 worked

using intel path
ANGLE (Intel(R) HD Graphics 3000 Direct3D11 vs_4_1 ps_4_1)
using amd path
ANGLE (Intel(R) HD Graphics 3000 Direct3D11 vs_5_0 ps_5_0)


I did also notice this did not change when swapping between the gpu's.

GPU0	VENDOR = 0x1002, DEVICE= 0x0000
GPU1	VENDOR = 0x8086, DEVICE= 0x0116 *ACTIVE* 

I though ANGLE was supposed to attempt the highest it could then fallback as failures occurred.

Also its worth mentioning AMD has set chrome.exe via profile to Intel adapter by default.

kbr@ is currently looking at this.

Sorry for not seeing this older bug, but re-enabling the D3D11 path for AMD switchable Windows machines with newer drivers under  Issue 755722 , so let me duplicate this into the other bug.