New issue
Advanced search Search tips

Issue 841789 link

Starred by 3 users
Status: Verified
Owner:
yang...@intel.com
Closed: Sep 6
Cc:
sande...@chromium.org
xhw...@chromium.org
liber...@chromium.org
rkuroiwa@chromium.org
yang...@intel.com
zmo@chromium.org
yunchao...@intel.com
mcasas@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression

Blocked on:
issue 879651
Blocking:
issue 838970
issue 843369



Sign in to add a comment

Builder Win10 FYI Exp Release (Intel HD 630): faliing webgl_conformance_d3d9_tests_on_Intel_GPU_on_Windows_on_Windows-10

Project Member Reported by rjkroege@chromium.org, May 10 2018 
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win10%20FYI%20Exp%20Release%20%28Intel%20HD%20630%29/14 (and on) have issues. Traces suggest something with the Windows media decoding support.

https://chromium.googlesource.com/chromium/src/+/15b5cf034c7758e0d25a407ff6e2d1e6c42473c8 and https://chromium.googlesource.com/chromium/src/+/ea55047ff9de7f0f5eb051f59a64c3271c205050 seem relevant.

GPU process bugs with vide decoder. 

[3948:2056:0509/181713.006:INFO:gpu_video_decode_accelerator_factory.cc(178)] Initializing DXVA HW decoder for windows.
Received fatal exception 0xc0000008
Backtrace:
	NtGdiDdDDIWaitForSynchronizationObjectFromCpu [0x75784D6C+c]
	(No symbol) [0x65E9A976]
	(No symbol) [0x65E94A70]
	(No symbol) [0x65E96CE3]
	(No symbol) [0x65EBCE6F]
	(No symbol) [0x65EB4AB8]
	(No symbol) [0x662EA1F5]
	(No symbol) [0x661C1F05]
	(No symbol) [0x661BDDA4]
	(No symbol) [0x661C4B41]
	(No symbol) [0x65FA4639]
	(No symbol) [0x65FA5A8A]
	(No symbol) [0x65FA4D5E]
	(No symbol) [0x65FA4572]
	(No symbol) [0x65EE5A52]
	(No symbol) [0x65EAB3EC]
	(No symbol) [0x69BD8B88]
	(No symbol) [0x69B0C611]
	(No symbol) [0x69AED852]
	(No symbol) [0x69D94111]
	media::DXVAVideoDecodeAccelerator::CopySurface [0x6D858992+280]
	base::internal::Invoker<base::internal::BindState<void (__thiscall media::DXVAVideoDecodeAccelerator::*)(IDirect3DSurface9 *,IDirect3DSurface9 *,int,int,gfx::ColorSpace const &),base::internal::UnretainedWrapper<media::DXVAVideoDecodeAccelerator>,base::in [0x6D85B81C+22]
	base::debug::TaskAnnotator::RunTask [0x6BB18784+134]
	base::internal::IncomingTaskQueue::RunTask [0x6BB45689+69]
	base::MessageLoop::RunTask [0x6BAFC8B7+207]
	base::MessageLoop::DeferOrRunPendingTask [0x6BAFCC0D+9d]
	base::MessageLoop::DoWork [0x6BAFCE3A+1fa]
	base::MessagePumpDefault::Run [0x6BB47CCC+9c]
	base::MessageLoop::Run [0x6BAFC3D4+74]
	base::RunLoop::Run [0x6BAC2E1C+cc]
	base::Thread::Run [0x6BAD6E04+a4]
	base::Thread::ThreadMain [0x6BAD7097+277]
	base::PlatformThread::SetCurrentThreadPriority [0x6BACAC45+215]
	BaseThreadInitThunk [0x74238674+24]
	RtlGetAppContainerNamedObjectPath [0x77834B47+137]
	RtlGetAppContainerNamedObjectPath [0x77834B17+107]
[928:1916:0509/181713.192:INFO:CONSOLE(0)] "WebGL: CONTEXT_LOST_WEBGL: loseContext: context lost", source: http://127.0.0.1:50492/third_party/webgl/src/sdk/tests/conformance/extensions/oes-texture-float-with-video.html (0)
[3340:5348:0509/181713.326:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:5348:0509/181713.326:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:5348:0509/181713.326:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:5348:0509/181713.326:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:5348:0509/181713.326:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:5348:0509/181713.326:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:5348:0509/181713.326:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:5348:0509/181713.326:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:5348:0509/181713.326:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:5348:0509/181713.326:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:5348:0509/181713.326:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:5348:0509/181713.326:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:5348:0509/181713.326:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:5348:0509/181713.326:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:5348:0509/181713.326:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:5348:0509/181713.326:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.329:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.329:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.329:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.329:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.329:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.329:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.329:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.329:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.329:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.330:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.330:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.330:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.330:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.330:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.330:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.330:ERROR:sync_point_manager.cc(248)] Client waiting on non-existent sync token
[3340:6696:0509/181713.330:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.334:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[3340:6696:0509/181713.338:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.339:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[3340:6696:0509/181713.339:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.342:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[3340:6696:0509/181713.353:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.353:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[3340:6696:0509/181713.355:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.355:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[3340:6696:0509/181713.355:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.355:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[3340:6696:0509/181713.359:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.359:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[3340:6696:0509/181713.359:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.359:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[3340:6696:0509/181713.359:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.359:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[3340:6696:0509/181713.359:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.359:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[3340:6696:0509/181713.359:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.361:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[3340:6696:0509/181713.363:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.363:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[3340:6696:0509/181713.363:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.363:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[3340:6696:0509/181713.363:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.363:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[3340:6696:0509/181713.363:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.363:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[3340:6696:0509/181713.364:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.364:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[3340:6696:0509/181713.364:ERROR:gles2_cmd_decoder.cc(18127)] [.DisplayCompositor-12E4FA10]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[3340:6696:0509/181713.364:ERROR:gles2_cmd_decoder.cc(10204)] [.DisplayCompositor-12E4FA10]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[8148:5332:0509/181713.191:FATAL:gpu_video_decode_accelerator_host.cc(116)] Check failed: false. Failed to duplicate buffer handler
Backtrace:
	base::debug::StackTrace::StackTrace [0x6BB1C080+32]
	base::debug::StackTrace::StackTrace [0x6BB0B1ED+13]
	logging::LogMessage::~LogMessage [0x6BA96B03+83]
	media::GpuVideoDecodeAcceleratorHost::Decode [0x6AE23B7A+282]
	media::GpuVideoDecoder::Decode [0x6ABE5BE1+1459]
	media::DecoderStream<2>::DecodeInternal [0x6ABD17D8+806]
	media::DecoderStream<2>::Decode [0x6ABD1478+322]
	media::DecoderStream<2>::OnBufferReady [0x6ABD2A9C+2084]
	base::internal::FunctorTraits<void (__thiscall media::DecoderStream<1>::*)(enum media::DemuxerStream::Status,scoped_refptr<media::DecoderBuffer>),void>::Invoke<void (__thiscall media::DecoderStream<1>::*)(enum media::DemuxerStream::Status,scoped_refptr<me [0x6ABD7D1E+58]
	base::internal::Invoker<base::internal::BindState<void (__thiscall media::DecoderStream<1>::*)(enum media::DemuxerStream::Status,scoped_refptr<media::DecoderBuffer>),base::WeakPtr<media::DecoderStream<1> > >,void __cdecl(enum media::DemuxerStream::Status, [0x6ABD7B71+65]
	base::OnceCallback<void __cdecl(enum media::Decryptor::Status,scoped_refptr<media::DecoderBuffer>)>::Run [0x6B98C965+51]
	base::internal::FunctorTraits<base::RepeatingCallback<void __cdecl(enum media::Decryptor::Status,scoped_refptr<media::DecoderBuffer>)>,void>::Invoke<base::RepeatingCallback<void __cdecl(enum media::Decryptor::Status,scoped_refptr<media::DecoderBuffer>)>,e [0x6ABDCE4C+116]
	base::internal::Invoker<base::internal::BindState<base::RepeatingCallback<void __cdecl(enum media::Decryptor::Status,scoped_refptr<media::DecoderBuffer>)>,enum media::Decryptor::Status,scoped_refptr<media::DecoderBuffer> >,void __cdecl(void)>::RunOnce [0x6ABDCDD3+23]
	base::debug::TaskAnnotator::RunTask [0x6BB18784+308]
	base::internal::IncomingTaskQueue::RunTask [0x6BB45689+105]
	base::MessageLoop::RunTask [0x6BAFC8B7+519]
	base::MessageLoop::DeferOrRunPendingTask [0x6BAFCC0D+157]
	base::MessageLoop::DoWork [0x6BAFCE3A+506]
	base::MessagePumpDefault::Run [0x6BB47CCC+156]
	base::MessageLoop::Run [0x6BAFC3D4+116]
	base::RunLoop::Run [0x6BAC2E1C+204]
	base::Thread::Run [0x6BAD6E04+164]
	base::Thread::ThreadMain [0x6BAD7097+631]
	base::PlatformThread::SetCurrentThreadPriority [0x6BACAC45+533]
	BaseThreadInitThunk [0x74238674+36]
	RtlGetAppContainerNamedObjectPath [0x77834B47+311]
	RtlGetAppContainerNamedObjectPath [0x77834B17+263]
Received fatal exception EXCEPTION_BREAKPOINT
Backtrace:
	base::debug::BreakDebugger [0x6BB223DC+12]
	?Run@?$Invoker@U?$BindState@P6AXPBDHV?$BasicStringPiece@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@base@@1@Z$$V@internal@base@@$$A6AXPBDHV?$BasicStringPiece@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@3@1@Z@internal@ [0x6CA8DAF1+31]
	logging::LogMessage::~LogMessage [0x6BA96F1D+1133]
	media::GpuVideoDecodeAcceleratorHost::Decode [0x6AE23B7A+282]
	media::GpuVideoDecoder::Decode [0x6ABE5BE1+1459]
	media::DecoderStream<2>::DecodeInternal [0x6ABD17D8+806]
	media::DecoderStream<2>::Decode [0x6ABD1478+322]
	media::DecoderStream<2>::OnBufferReady [0x6ABD2A9C+2084]
	base::internal::FunctorTraits<void (__thiscall media::DecoderStream<1>::*)(enum media::DemuxerStream::Status,scoped_refptr<media::DecoderBuffer>),void>::Invoke<void (__thiscall media::DecoderStream<1>::*)(enum media::DemuxerStream::Status,scoped_refptr<me [0x6ABD7D1E+58]
	base::internal::Invoker<base::internal::BindState<void (__thiscall media::DecoderStream<1>::*)(enum media::DemuxerStream::Status,scoped_refptr<media::DecoderBuffer>),base::WeakPtr<media::DecoderStream<1> > >,void __cdecl(enum media::DemuxerStream::Status, [0x6ABD7B71+65]
	base::OnceCallback<void __cdecl(enum media::Decryptor::Status,scoped_refptr<media::DecoderBuffer>)>::Run [0x6B98C965+51]
	base::internal::FunctorTraits<base::RepeatingCallback<void __cdecl(enum media::Decryptor::Status,scoped_refptr<media::DecoderBuffer>)>,void>::Invoke<base::RepeatingCallback<void __cdecl(enum media::Decryptor::Status,scoped_refptr<media::DecoderBuffer>)>,e [0x6ABDCE4C+116]
	base::internal::Invoker<base::internal::BindState<base::RepeatingCallback<void __cdecl(enum media::Decryptor::Status,scoped_refptr<media::DecoderBuffer>)>,enum media::Decryptor::Status,scoped_refptr<media::DecoderBuffer> >,void __cdecl(void)>::RunOnce [0x6ABDCDD3+23]
	base::debug::TaskAnnotator::RunTask [0x6BB18784+308]
	base::internal::IncomingTaskQueue::RunTask [0x6BB45689+105]
	base::MessageLoop::RunTask [0x6BAFC8B7+519]
	base::MessageLoop::DeferOrRunPendingTask [0x6BAFCC0D+157]
	base::MessageLoop::DoWork [0x6BAFCE3A+506]
	base::MessagePumpDefault::Run [0x6BB47CCC+156]
	base::MessageLoop::Run [0x6BAFC3D4+116]
	base::RunLoop::Run [0x6BAC2E1C+204]
	base::Thread::Run [0x6BAD6E04+164]
	base::Thread::ThreadMain [0x6BAD7097+631]
	base::PlatformThread::SetCurrentThreadPriority [0x6BACAC45+533]
	BaseThreadInitThunk [0x74238674+36]
	RtlGetAppContainerNamedObjectPath [0x77834B47+311]
	RtlGetAppContainerNamedObjectPath [0x77834B17+263]
Found crashpad_database_util
Minidump found: c:\b\s\w\itwhbvnd\tmp7plnfj\reports\c157437f-2db1-461d-9ad8-4c66667c9748.dmp
Uploading c:\b\s\w\itwhbvnd\tmp7plnfj\reports\c157437f-2db1-461d-9ad8-4c66667c9748.dmp to gs://chrome-telemetry-output/minidump-2018-05-09_18-17-13-670161.dmp

Comment 1 by xhw...@chromium.org, May 10 2018

Cc: xhw...@chromium.org sande...@chromium.org
Owner: liber...@chromium.org
liberato: Could you please help take a look?

Comment 2 by kbr@chromium.org, May 10 2018

Blocking: 838970
Cc: yang...@intel.com zmo@chromium.org yunchao...@intel.com
Note: this bot is running Intel's latest graphics driver for Windows, compared to this one:
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win10%20FYI%20Release%20(Intel%20HD%20630)

which is running the next oldest version.

We suspect that the crashes in DXVA on D3D9 are due to newly introduced bugs in the driver, but if there's a bug in Chrome's code that's causing this crash then it would certainly be worth fixing, as it looks like any Chrome user who falls back to the D3D9 backend will have broken video support.

Not sure whether this is P1, but leaving it at that priority for now.

Comment 3 by jdarpinian@chromium.org, May 15 2018

Blocking: 843369
Project Member

Comment 4 by bugdroid1@chromium.org, May 16 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/5ab0c6255a2d7bba4055d84dba2a15286de2d0d8

commit 5ab0c6255a2d7bba4055d84dba2a15286de2d0d8
Author: James Darpinian <jdarpinian@chromium.org>
Date: Wed May 16 01:11:48 2018

Disable failing tests on experimental Intel driver

Bug:  843369 , 841789 
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: Id6c695fc7aa3e4ae3019d3b82568dd1453385ebb
Reviewed-on: https://chromium-review.googlesource.com/1060521
Commit-Queue: James Darpinian <jdarpinian@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558909}
[modify] https://crrev.com/5ab0c6255a2d7bba4055d84dba2a15286de2d0d8/content/test/gpu/generate_buildbot_json.py
[modify] https://crrev.com/5ab0c6255a2d7bba4055d84dba2a15286de2d0d8/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py
[modify] https://crrev.com/5ab0c6255a2d7bba4055d84dba2a15286de2d0d8/testing/buildbot/chromium.gpu.fyi.json

Comment 5 by yang...@intel.com, May 29 2018 

This issue was reported on driver 24.20.100.6025 (https://downloadcenter.intel.com/download/27680/Graphics-Intel-Graphics-Driver-for-Windows-10?product=80939). I just checked a newly updated driver 24.20.100.6094 (https://downloadcenter.intel.com/download/27803/Graphics-Intel-Graphics-Driver-for-Windows-10?product=80939), and this issue was still there.

Comment 6 by kbr@chromium.org, May 29 2018

Labels: -Type-Bug Type-Bug-Regression
Thanks for checking Yang. Is Intel's D3D9 driver team looking into this issue? It seems serious because Chrome's video playback is likely broken in this configuration. Again, not sure whether this is ultimately a bug in Chrome's video stack, but it's certainly a regression.

Comment 7 by kbr@chromium.org, May 29 2018

Labels: GPU-Intel

Comment 8 by yang...@intel.com, May 30 2018 

I reported this issue to our driver team 2 weeks ago. They have found the CL in driver that introduced the regression, and are now working on a fix. Thus Chrome is supposed to be good on this case:)

Comment 9 by kbr@chromium.org, May 30 2018

Status: ExternalDependency (was: Assigned)
Thank you Yang, that's great news!

liberato@: marking this ExternalDependency as it sounds like there is no work for you to do.

Comment 10 by zmo@chromium.org, May 30 2018 

We should probably blacklist video decoding on D3D9 with the affected driver version(s).

Comment 11 by xhw...@chromium.org, May 30 2018 

zmo: Good point! What's the recommended way to blacklist a bad driver version?

Comment 12 by zmo@chromium.org, May 31 2018 

gpu/config/software_rendering_list.json

You want to use the feature "accelerated_video_decode". There are a lot of examples, so you can easily figure out the semantic for a new entry.

Comment 13 by zmo@chromium.org, May 31 2018 

And you need to add a condition for GL_RENDERER to have *Direct3D9*, so we don't accidentally blacklist D3D11.

Comment 14 by yang...@intel.com, Aug 31 

This issue (Actually there are 2 issues here) was fixed by Intel graphics driver, and the release 2 days ago (24.20.100.6286, https://downloadcenter.intel.com/download/27988/Intel-Graphics-Driver-for-Windows-10?product=80939) contained the fix. I ran all the tests (WebGL1 D3D9, WebGL1 D3D11 and WebGL2 D3D11) against r581550 and r587865 today, and all the cases passed. 
So I suggest to upgrade the driver at your side. 
Note that the previous driver, 24.20.100.6229, didn't fix the issue. I.e., 24.20.100.6286 is the first public driver to fix this issue.

Comment 15 by kbr@chromium.org, Aug 31

Blockedon: 879651

Comment 16 by kbr@chromium.org, Aug 31 

Thank you Yang! Asked the Labs team to upgrade the driver ASAP.

Comment 17 by kbr@chromium.org, Sep 5 

Now that the driver's been upgraded, re-enabling the failing WebGL D3D9 tests on this bot in this CL:
https://chromium-review.googlesource.com/1207652
Project Member

Comment 18 by bugdroid1@chromium.org, Sep 5 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a784487fa9de31752d24bff0871c3cbf451097de

commit a784487fa9de31752d24bff0871c3cbf451097de
Author: Kenneth Russell <kbr@chromium.org>
Date: Wed Sep 05 20:21:27 2018

Re-enable previously failing tests on Win10 Intel Exp bot.

After the update to the 24.20.100.6286 driver, these tests should be
passing. Re-enable:
  webgl_conformance_d3d9_tests
  webgl_conformance_d3d9_passthrough_tests
  conformance2/glsl3/short-circuiting-in-loop-condition.html

Tbr: zmo@chromium.org
Bug:  841789 ,  843369 
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I1ec732be8a283c2fdb68bf316943ee2d7d0b65b1
Reviewed-on: https://chromium-review.googlesource.com/1207652
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588987}
[modify] https://crrev.com/a784487fa9de31752d24bff0871c3cbf451097de/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py
[modify] https://crrev.com/a784487fa9de31752d24bff0871c3cbf451097de/testing/buildbot/chromium.gpu.fyi.json
[modify] https://crrev.com/a784487fa9de31752d24bff0871c3cbf451097de/testing/buildbot/test_suite_exceptions.pyl

Comment 19 by kbr@chromium.org, Sep 6

Status: Verified (was: ExternalDependency)
These tests are passing now on this bot:
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win10%20FYI%20Exp%20Release%20%28Intel%20HD%20630%29?limit=200

Here was the first build where they ran again:
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win10%20FYI%20Exp%20Release%20%28Intel%20HD%20630%29/1233

Closing as Verified. Thank you Yang and your team for helping get this regression fixed!

Comment 20 by kbr@chromium.org, Sep 6

Cc: liber...@chromium.org
Owner: yang...@intel.com
(Reassigning bug to Yang to show credit for the fix)

Comment 21 by yang...@intel.com, Sep 7 

Glad to know this can be verified at your side. A quite long journey with a happy ending, especially we will seldom see this kind of regression:)
►

Sign in to add a comment