the problem occurred immediately after upgrading to v.64 from 63.
of course, fresh install, new user, delete cache, restore settings, delete plugins etc. not working.

Thanks for filing the issue!

Unable to reproduce the issue on reported chrome version 65.0.3325.146 using Windows 10 with the below mentioned steps.
1. Launched Chrome
2. Navigated to https://www.youtube.com/watch?v=iLUcmC_OBLY
We are able to play the video by HW acceleration ON and OFF. 

@Reporter: Could you please have a look at the screen cast and let us know if anything missed from our end. Could you please detail us on "codec avc 1.4.x.x" as we are not clear on the environment in which the issue can be reproduced. Any further inputs from your end may help us.

Deleted: 820643.mp4 2.5 MB

	820643.mp4 2.5 MB View Download

When clips using codec avc, that issue exist. All clips using codec vp working good. It is noticed regularity.
(open yt clips > right mouse button on screen > nerd stats to check)

I noticed one more dependence. Most users have mobility ATI graphics.

Your embedded video it also does not show up with hard accel.
All clips in ver63 working ok.

This is how it looks now:

Deleted: VP OK Mar 12 2018 3_56 PM.webm 449 KB

	VP OK Mar 12 2018 3_56 PM.webm 449 KB View Download

Deleted: AVC BAD Mar 12 2018 3_58 PM.webm 394 KB

	AVC BAD Mar 12 2018 3_58 PM.webm 394 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Re-tested the issue on reported version 65.0.3325.146 using Windows 10 with link https://www.youtube.com/watch?v=iLUcmC_OBLY , observing successful play of video without any breakage. Attaching screencast for reference.

@Reporter: Please check the video and let us know if we miss anything. Is this happening in Incognito profile or fresh profile which do not have any apps/extensions. Any further info on reproducing this issue will help in further investigation.

Thanks! 

Deleted: 820643.mp4 3.2 MB

	820643.mp4 3.2 MB View Download

Deleted: gpu-M65.html 119 KB

gpu-M65.html 119 KB View Download

^^
You dont miss anything.

I try again and again after every update. Now on 65.0.3325.162 still the same.
Of course i try fresh install without any extension, even on 2 different windows account/users with administrator privileges. Up to v63 ok, 64-65 not.
I suspect, something change in chrome in video support after v63.

I'm not alone with it. I have more confirmations from many other threads, that this problem occurs exactly like in my case.
broken yt: https://www.youtube.com/watch?v=i8r70g-Kanc  
and vimeo: https://vimeo.com/channels/staffpicks/259878665

It looks like, on some configurations this issue exist.
What else can I do? If u want any specific informations, I try to do in my best.

I made friends with chrome a few years ago. I would not want to give up on him.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Hello.
Work in progress. I found another "solutions".
I try lot of #flags settings relating to graphic render and find something.

link: chrome://flags/#disable-software-rasterizer

--
3D software rasterizer.
Fall back to a 3D software rasterizer when the GPU cannot be used. – Mac, Windows, Linux, Chrome OS, Android
#disable-software-rasterizer
--

In v65 default options is Enabled. I change this to Disabled.
And now, with Enabled Hardware Accel, all linked broken video on yt, vimeo and other WORKING OK!

Maybe it will suggest something solutions.

Can anyone check the default this settings in chrome v63?

pre757@ Thanks for the feedback.

Tested this issue on Windows 10 on M-65 build 65.0.3325.146 and M-63 build 63.0.3239.132 as per comment #10.

Played the given video on Youtube with 'Hardware Acceleration' Enabled and '3D software rasterizer' Enabled and Disabled and could observe that the video is played without any breakage.
Attached are the screen casts for reference.

Request you to check the issue on a new chrome profile without any files/extensions and update the thread with the observations.

Thanks.. 

Deleted: 820643-M63.mp4 3.6 MB

	820643-M63.mp4 3.6 MB View Download

Deleted: 820643-M65.mp4 2.3 MB

	820643-M65.mp4 2.3 MB View Download

Hi Susan.

New profile, fresh installations, chrome cleanup tool and other simple things... they bring nothing new. Is not a problem with that.

Problem mostly occurs when ATI card installed (lot of cases, here HD4500 series).
On your system is probably fine, but many systems have this issue indisputably. Many post on chrome forum with exactly the same symptoms, this isnt single coincidence.
Need to try combinations with ATI card.
This happend definitly after chrome update to v64.

Quite possibly that only for this hardware configurations this issue exist.
Different specs working good regardless of settings '3d soft' and 'hard accel'.

Anyway, we wait for some chrome update, and we look for W10 Spring Creators Update.
Maybe graphics management in windows will be changed. Thats last hope as i see.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Additional info for my last post.

I was right about the settings.
As i sad, problem occurs after update from v63 to v64.
And screenshot says why.

In v63 '3D software rasterizer' default is Disabled. Thats why all video working properly.
After update (in v64-65), default is Enabled.

What interesting, in v63 on both settings '3D software rasterizer' (enabled & disabled) video looks good :-)

Now, questions is why...

Deleted: Chrome 63 Flag.PNG 14.1 KB

	Chrome 63 Flag.PNG 14.1 KB View Download

even with both "3D software rasterizer" and "hardware accelerated video decode" enabled, I still couldn't repro this bug on my Windows+Chrome 67.
what is your graphic card?

Card build in notebook, ATI Mobility Radeon™ HD 4570.
Lot od cases with this problem has ATI card.

See up posts for more informations.

Hmmm, GPU folks, did this card get removed from hardware compositing blacklist somehow in 64+?

Reporter: Can you try running Chrome with --disable-direct-composition flag, and hardware acceleration *enabled*?

Test team: Do we have a laptop with this GPU?

Mo: Does the AMD laptop you got have this GPU?

No, the one I have is a different GPU, and no, testing team doesn't have a Windows laptop with this AMD GPU when I checked a few days ago

"Can you try running Chrome with --disable-direct-composition flag"

Yes. And seems to be ok.
Summary on chrome ver. 65.0.3325.181

Default chrome run:
1) hardware accel > Enabled
   3D software rasterizer > Enabled
= video broken

2) hardware accel > Enabled
   3D software rasterizer > Disabled
= video working OK, but video 360' dont.


Chrome run with shortcut "--disable-direct-composition":
   hardware accel > Enabled
   3D software rasterizer > Enabled
= all video correct, 360' also

sample used to test:
https://www.youtube.com/watch?v=iLUcmC_OBLY
https://vimeo.com/channels/staffpicks/259878665
360': https://www.youtube.com/watch?v=dzfUnYKXq9w

As per comment #19 & 20, Windows 10 machine with AMD gpu is not available at TE end to test this issue.

Hence adding TE-NeedsTriageFromMTV for further help in triaging this issue.

Thanks..

// Adding to comment #22.

Removing Needs-TestConfirmation label as the setup is not available at TE end to confirm the issue.

Thanks..

pre757 can you post contents of chrome://crashes please?

I suspect our DirectCompsotion code crashes on your system, and we fallback to software rasterizer (swiftshader). Somehow this doesn't work correctly with certain video codecs. So there are two distinct bugs:

1. Disable DirectComposition code path if it keeps failing consistently instead of disabling GPU acceleration completely.
2. Make swiftshader work with the specific codec that's failing.

We'll investigate 2 as part of this bug, and I'll file a separate bug for 1.

There is no informations in chrome://crashes. It's blank.

I test on all broken clips. Video not propertly, sound ok.
Now, version 66.0.3359.117 exactly the same like before.
Test settings in Comment #21: https://bugs.chromium.org/p/chromium/issues/detail?id=820643#c21

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Issue, already been assigned, removing MTV label.

Hello!
Looks like direct composition mode doesn't work on Radeon.
We have a lot reports from users with Radeon with 'ContextResult::kFatalFailure: Failed to create surface.' in GPU logs.
We be able to reproduce this problem on notebook with Radeon.
Do we need to blacklist direct composition on Radeon?

#29 can you help us with debugging? if you run a debug build of ToT with --enable-logging=stderr, you might find one of the error logs in src/gpu/ipc/service/direct_composition_surface_win.cc.

pre757, can you also try the --disable-accelerated-video-decode flag (without other flags) and let us know if you can reproduce the issue?

Summary of the above comments:
1. AVC 1.4 (h264) video is broken but VP9 video works fine. h264 probably uses hardware decoding, and VP9 does not?
2. chrome://gpu has 'ContextResult::kFatalFailure: Failed to create surface.'
3. Disabling software rasterizer (swiftshader) fixes the problem. Software rasterizer flag was introduced in M64.
4. Affected hardware is at least Radeon mobility HD 4500.

+dalecurtis,liberato: any ideas?

media folks, does this bit from chrome://gpu mean VP9 hardware decoding is supported:

Video Acceleration Information
Decode h264 baseline	up to 1920x1088 pixels
Decode h264 main	up to 1920x1088 pixels
Decode h264 high	up to 1920x1088 pixels
Decode vp8	up to 4096x2160 pixels
Decode vp9 profile0	up to 4096x2160 pixels
Decode vp9 profile1	up to 4096x2160 pixels
Decode vp9 profile2	up to 4096x2160 pixels
Decode vp9 profile3	up to 4096x2160 pixels
Encode h264 baseline	up to 3840x2176 pixels and/or 30.000 fps
Encode h264 main	up to 3840x2176 pixels and/or 30.000 fps
Encode h264 high	up to 3840x2176 pixels and/or 30.000 fps

Can you grab the chrome://gpu from canary? There were some bugs in the past that are now fixed with that listing. You can check a VP9 playback on YouTube and see if you end up with GpuVideoDecoder in chrome://media-internals.

That said, I don't think an AMD 4500 from 2015 has a VP9 hardware decoder....

What can i say...
My laptop with radeon died 2 weeks ago. After 9 years hard work ~18h/day.
Now, new with intel+nvidia.

FWIW here's the product forum thread for this issue: https://productforums.google.com/forum/#!topic/chrome/1w3TXNHUTE4

In ImageTransportSurface::CreateNativeSurface ( https://cs.chromium.org/chromium/src/gpu/ipc/service/image_transport_surface_win.cc?dr&q=ImageTransportSurface::CreateNativeSurface&sq=package:chromium&g=0&l=42 ):
gl::GetGLImplementation() == gl::kGLImplementationEGLGLES2,
gl::GLSurfaceEGL::IsDirectCompositionSupported() == true,
call egl_surface->Initialize() return false.

In DirectCompositionSurfaceWin::Initialize ( https://cs.chromium.org/chromium/src/gpu/ipc/service/direct_composition_surface_win.cc?type=cs&q=DirectCompositionSurfaceWin::Initialize&g=0&l=1397 ):
layer_tree_->Initialize(window_) return false.

In DCLayerTree::Initialize ( https://cs.chromium.org/chromium/src/gpu/ipc/service/direct_composition_surface_win.cc?type=cs&q=DCLayerTree::Initialize&g=0&l=366 ):
d3d11_device_.CopyTo(video_device_.GetAddressOf() return HRESULT = 0x80004002.

From DX Error Lookup:
HRESULT: 0x80004002 (2147500034)
Name: E_NOINTERFACE
Description: The requested COM interface is not available
Severity code: Failed
Facility Code: FACILITY_NULL (0)
Error Code: 0x4002 (16386)

That call shouldn't normally fail.

From ID3D11VideoDevice docs: https://msdn.microsoft.com/en-us/library/windows/desktop/hh447781(v=vs.85).aspx

> Remarks
> The Direct3D 11 device supports this interface. To get a pointer to this interface, call QueryInterface with an ID3D11Device interface pointer.
>
> If you query an ID3D11Device for ID3D11VideoDevice and the Direct3D 11 device created is using the reference rasterizer or WARP, or is a hardware device and you are using the Microsoft Basic Display Adapter, E_NOINTERFACE is returned."

Anyway, I'm planning on making this logic more robust so that we can downgrade gracefully if one of these calls fail. It's still concerning that swiftshader somehow fails with avc video.

E_NOINTERFACE returned on Radeon notebook, not Microsoft Basic Display Adapter.
I will attach gpu info tomorrow.

immediate fix here: crrev.com/c/1080213

Since the failing call is QueryInterface of ID3D11VideoDevice, it's conceivable other video decoding stuff is broken on this hardware.

chrome://gpu from radeon notebook

Deleted: gpu.htm 171 KB

gpu.htm 171 KB View Download

Hi all. Any updates since the last message?
Today I tried Opera, Vivaldi, Chrome - everywhere the videos fail in the following combination: Win10 (32 or 64 bit - does not matter), enabled hardware accelleration, Toshiba Satellite A300 with ATI Mobility Radeon HD 3470 videocard with Microsoft drivers (that have not been updated for many years)
I also tied Win 7 - everything is ok there on 32 or 64 bit even with Hardware Acceleration

And the question
when I run Opera with "--disable-direct-composition" and Hardware acceleration enabled - all seems to be fine
Does it mean, that in this case hardware acceleration works, but with some restrictions. And better using with "--disable-direct-composition" and hardware acceleration enabled, then simply remove hardware acceleration from settings?

Most likely a dupe of  issue 800950 

from the forum thread (link in #34): it seems once users disable SwiftShader, things begin to work.

So there are two issues:

1) why the affected machines fall back to SwiftShader? either WebGL gets blacklisted on their machines, or GPU process crashed too many times

2) it seems SwiftShader doesn't work for these video site. +capn@, +sugoi@

I wonder if there's any relation to  issue 859946  and this should be expanded to all platforms:
https://cs.chromium.org/chromium/src/content/renderer/media/gpu/gpu_video_accelerator_factories_impl.cc?l=397

Hello!
Do you have some news about comment #38? Why this fix was not applied?

We have a better fix coming up: https://chromium-review.googlesource.com/c/chromium/src/+/1278529

That CL will disable direct composition code completely if hardware overlays are not supported.  We perform the video device initialization check as a part of checking for hardware overlays.