GPU Video Acceleration Disabled with AMD Switchable Graphics
Reported by
ie.de201...@gmail.com,
Jan 31 2017
|
||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36 Example URL: https://www.youtube.com/watch?v=iNJdPyoqt8U&t=29s Steps to reproduce the problem: 1. Use H264ify extension to make sure youtube viedo use H264 codec not VP9 2. 3. What is the expected behavior? 4K video should play smoothly and use less CPU usage What went wrong? 4k video stutters and high CPU usage Did this work before? N/A Is it a problem with Flash or HTML5? HTML5 Does this work in other browsers? Yes Chrome version: 56.0.2924.76 Channel: stable OS Version: 10.0.14393 Flash Version: Shockwave Flash 24.0 r0 Contents of chrome://gpu: Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Software only, hardware acceleration unavailable Flash Stage3D: Software only, hardware acceleration unavailable Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable Compositing: Software only, hardware acceleration unavailable Multiple Raster Threads: Unavailable Native GpuMemoryBuffers: Software only. Hardware acceleration disabled Rasterization: Software only, hardware acceleration unavailable Video Decode: Software only, hardware acceleration unavailable Video Encode: Software only, hardware acceleration unavailable VPx Video Decode: Software only, hardware acceleration unavailable WebGL: Unavailable WebGL2: Unavailable Driver Bug Workarounds clear_uniforms_before_first_program_use disable_d3d11 disable_discard_framebuffer disable_framebuffer_cmaa exit_on_context_lost force_cube_complete msaa_is_slow scalarize_vec_and_mat_constructor_args texsubimage_faster_than_teximage Problems Detected GPU process was unable to boot: Features are disabled on full but not preliminary GPU info. Disabled Features: all GPU rasterization should only be enabled on NVIDIA Pascal and Maxwell, Intel Broadwell+, and AMD RX-R5 GPUs for now.: 643850 Disabled Features: gpu_rasterization Accelerated VPx decoding is hanging on some videos.: 654111 Disabled Features: accelerated_vpx_decode Some drivers are unable to reset the D3D device in the GPU process sandbox Applied Workarounds: exit_on_context_lost TexSubImage is faster for full uploads on ANGLE Applied Workarounds: texsubimage_faster_than_teximage Clear uniforms before first program use on all platforms: 124764, 349137 Applied Workarounds: clear_uniforms_before_first_program_use Always rewrite vec/mat constructors to be consistent: 398694 Applied Workarounds: scalarize_vec_and_mat_constructor_args Disable Direct3D11 on systems with AMD switchable graphics: 451420 Applied Workarounds: disable_d3d11 ANGLE crash on glReadPixels from incomplete cube map texture: 518889 Applied Workarounds: force_cube_complete On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565 Applied Workarounds: msaa_is_slow Framebuffer discarding can hurt performance on non-tilers: 570897 Applied Workarounds: disable_discard_framebuffer Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198 Applied Workarounds: disable_framebuffer_cmaa Native GpuMemoryBuffers have been disabled, either via about:flags or command line. Disabled Features: native_gpu_memory_buffers Version Information Data exported 1/31/2017, 9:49:56 AM Chrome version Chrome/56.0.2924.76 Operating system Windows NT 10.0.14393 Software rendering list version 12.06 Driver bug list version 9.24 ANGLE commit id 555009cefe4c 2D graphics backend Skia/56 bf2d9e02d58ea01f1c239f7e2fc024cba140ccb1 Command Line Args Files (x86)\Google\Chrome\Application\chrome.exe" --flag-switches-begin --flag-switches-end Driver Information Initialization time 114 In-process GPU false Sandboxed true GPU0 VENDOR = 0x1002, DEVICE= 0x666f GPU1 VENDOR = 0x8086, DEVICE= 0x0a16 *ACTIVE* Optimus false AMD switchable true Desktop compositing Aero Glass Diagonal Monitor Size of \\.\DISPLAY5 13.9" Driver vendor Advanced Micro Devices, Inc. Driver version 15.200.1045.0 Driver date 6-22-2015 Pixel shader version 3.0 Vertex shader version 3.0 Max. MSAA samples 8 Machine model name Machine model version GL_VENDOR Google Inc. GL_RENDERER ANGLE (Intel(R) HD Graphics Family Direct3D9Ex vs_3_0 ps_3_0) GL_VERSION OpenGL ES 2.0 (ANGLE 2.1.0.555009cefe4c) GL_EXTENSIONS GL_ANGLE_depth_texture GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_pack_reverse_row_order GL_ANGLE_robust_client_memory GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_sync_query GL_EXT_blend_minmax GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_frag_depth GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_shader_texture_lod GL_EXT_texture_compression_dxt1 GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_NV_fence GL_NV_pack_subimage GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object Disabled Extensions Window system binding vendor Google Inc. (adapter LUID: 000000000027bbe0) Window system binding version 1.4 (ANGLE 2.1.0.555009cefe4c) Window system binding extensions EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_EXT_device_query EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource Direct rendering Yes Reset notification strategy 0x8252 GPU process crash count 0 Compositor Information Tile Update Mode One-copy Partial Raster Enabled GpuMemoryBuffers Status ATC Software only ATCIA Software only DXT1 Software only DXT5 Software only ETC1 Software only R_8 Software only RG_88 Software only BGR_565 Software only RGBA_4444 Software only RGBX_8888 Software only RGBA_8888 Software only BGRX_8888 Software only BGRA_8888 Software only YVU_420 Software only YUV_420_BIPLANAR Software only UYVY_422 Software only Diagnostics ... loading ... Log Messages WARNING: Hardware acceleration is unavailable. I have a laptop with Intel HD Graphics 4400 and AMD Radeon R5 M230 Switchable graphics. 1. from chrome://gpu tab, at default all graphics feature states are software only (see gpu_IntelAMD.html). This results playing 4K video in H264 codec stutters. 2. If "Override software rendering list" enabled in chrome://flags, all graphics feature states are hardware accelerated in chrome://gpu (see gpu_IntelAMD_ignoregpublacklist.html) BUT actual 4K playback from youtube stutters. Which means same behavior like "Override software rendering list" disabled. 3. I tried to uninstall the AMD driver so only Intel HD Graphics 4400 detected, and all graphics feature states are hardware accelerated in chrome://gpu (see gpu_IntelOnly.html). Playing 4K video in H264 codec is smooth with low CPU usage. Tried same video in Microsoft EDGE with both drivers enabled and it doesn't stutters and have low CPU usage. So when AMD driver is installed, chrome doesn't get hardware acceleration from Intel HD Graphics 4400. Attached dxdiag information and chrome://gpu tab contents for each configuration.
,
Jan 31 2017
Thanks for all the diagnostic info, it's very helpful. > Did this work before? N/A Do you know if this problem is new in Chrome 56? (Has the behavior regressed?) ---- This is really a GPU problem, not just media; the GPU process isn't running. Here is the source of that detected problem string: https://cs.chromium.org/chromium/src/content/browser/gpu/gpu_data_manager_impl_private.cc?l=376&rcl=8422bf10bc4af33a0db2fde5117792ecde362863 zmo seems to have worked on this code; CC'd. This is an interesting case because the GPU0 is AMD and GPU1 is Intel. (The opposite order seems more common. I wonder if there's a bug in that configuration?)
,
Jan 31 2017
,
Feb 1 2017
Hi zmo, Thanks for your answer, regarding your question : Do you know if this problem is new in Chrome 56? (Has the behavior regressed?) - I had Chrome 54 & 55 before and it had same behavior like Chrome 56. Not sure about Chrome < 54 though. Yes, I realize that when both Intel & AMD drivers are installed, the GPU order is : - GPU0 : AMD - GPU1 : Intel (Active) But, if only Intel driver is installed, the GPU order is : - GPU0 : Intel (Active) The order seems a little bit off for me so maybe that causes the problem? I have another laptop with NVIDIA optimus and the GPU order is : - GPU0 : Intel (Active) - GPU1 : NVIDIA and of course, hardware acceleration works perfectly there. Maybe Chrome only take GPU0 hardware acceleration? So in my case, because Intel is in GPU1, the hardware acceleration is not available for Chrome.
,
Feb 2 2017
,
Feb 3 2017
Can you run with --user-data-dir=\some\temp\folder and see if it fixes your issue?
,
Feb 3 2017
I think the root cause of this is """ GPU process was unable to boot: Features are disabled on full but not preliminary GPU info. Disabled Features: all Accelerated VPx decoding is hanging on some videos.: 654111 Disabled Features: accelerated_vpx_decode """ accelerated_vpx_decode is disabled on Intel with older drivers. However, the driver version we got is AMD driver version. This is a messed up situation in our GPU info collection.
,
Feb 3 2017
Maybe we need to switch this to a gpu driver bug workaround rather than a blacklist entry. The GPU process communicates the outcome directly to the renderers, so the browser shouldn't need to decide anything.
,
Feb 4 2017
I agree with jbauman's proposal - so we could compute it on the GPU process side. jbauman: can you take this bug? ie.de201941@gmail.com: if you update your Intel drivers to the latest, on which accelerated_vpx_decode is enabled, then you will not suffer from this issue.
,
Feb 4 2017
Hi zmo, Attached chrome://gpu tab with --user-data-dir=\some\temp\folder flag. Issue is not fixed. Also, I use the latest driver available from Intel but hardware acceleration still not available. The only thing to make sure that hardware acceleration is enabled is to uninstall AMD driver but. With only Intel driver installed, accelerated_vpx_decode is still software rendered because Intel HD 4400 doesn't support VP9 full hardware decode. From my previous post, when both drivers are installed and "Override software rendering list" enabled, all graphics features are hardware accelerated (accelerated_vpx_decode included) but the performance is similar with "Override software rendering list" disabled which means the hardware acceleration is not actually enabled.
,
Feb 10 2017
,
Feb 23 2017
I agree that it sounds like the accelerated_vpx_decode entry needs tweaking, but I'm curious why we also got "GPU process was unable to boot: Features are disabled on full but not preliminary GPU info.", are there multiple issues here?
,
Feb 23 2017
Issue 695191 has been merged into this issue.
,
Apr 10 2017
I'm affected by this issue for at least 6 months. This is when I noticed that Chrome is showing tearing effect when scrolling some pages. Scrolling on some webpages is slow too. The symptoms are exactly the same as described above. Please find chrome://gpu log attached. You'll notice some experiments enabled but the same issue occurs with a clean profile on any branch - stable, beta, dev, canary. I lived with the "Override software rendering list" flag for some time but since Chrome 57 something changed/regressed and now with this option Chrome "bubbles" such as "Allow this website to show notifications" with Allow and Block buttons are not drawn and the whole UI becomes stuck as a result. I couldn't even easily remove the browser after this because it looks like the dialog where you can select an option to clear your profile on uninstall is affected by the same issue as well. GPU acceleration works fine in Firefox and Microsoft Edge on this machine. As you can see from the log, I'm on the latest drivers available as well as using latest 15063.13 build of Windows 10. Right now I'm experiencing a very degraded and poor experience. 2K videos on YouTube eat around 70% of CPU when Edge is at 7-10% at most. Scrolling is sometimes painful. Overall, I feel like the browser is struggling to do its job. I'm not sure how prevalent this configuration is to prioritize this but please fix this asap if possible. Thank you.
,
Apr 10 2017
Sorry for spamming the comments section but I noticed that chrome://gpu didn't include the driver version of my iGPU: 21.20.16.4550 which is important because #c7 here referred to issue 654111 where it is mentioned in #c25, #c26 that driver versions > 21.20.16.4542 should work fine with hardware decoding which #c7 of this issue assumes to be the culprit. Thanks.
,
Apr 30 2017
A quick update. --ignore-gpu-blacklist seems to be working now in 59.0.3071.29 (Official Build) beta (64-bit) (cohort: Beta All Delta). No issues with the UI whatsoever compared to my previous description. Again, this is a workaround. Out of the box GPU acceleration is disabled without this flag even though the system is adequately capable of GPU accelerated rendering of the content. Please see a chrome://gpu log attached.
,
May 4 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/beabb626561e9899cb3099b3c7cd5a1447bf00f7 commit beabb626561e9899cb3099b3c7cd5a1447bf00f7 Author: jbauman <jbauman@chromium.org> Date: Thu May 04 23:22:57 2017 Make disabling accelerated VPX decoding a GPU driver bug workaround. This is currently a blacklist entry, which means that it's calculated in the browser and the resulting decision could be incorrect if the GPU process uses a different GPU from what the browser expects. If this is a GPU driver bug workaround entry then it'll be determined with more information in the GPU process. BUG= 687004 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Review-Url: https://codereview.chromium.org/2682723003 Cr-Commit-Position: refs/heads/master@{#469513} [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/content/browser/gpu/compositor_util.cc [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/content/browser/gpu/gpu_data_manager_impl_private.cc [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/content/browser/gpu/gpu_data_manager_testing_arrays_and_structs_autogen.h [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/gpu/config/gpu_blacklist.cc [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/gpu/config/gpu_blacklist_unittest.cc [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/gpu/config/gpu_driver_bug_list.json [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/gpu/config/gpu_driver_bug_workaround_type.h [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/gpu/config/gpu_feature_type.h [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/gpu/config/software_rendering_list.json [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/gpu/ipc/service/gpu_channel_manager.cc [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/gpu/ipc/service/gpu_channel_manager.h [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/gpu/ipc/service/gpu_channel_test_common.cc [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/media/gpu/dxva_video_decode_accelerator_win.cc [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/media/gpu/dxva_video_decode_accelerator_win.h [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/media/gpu/gpu_video_decode_accelerator_factory.cc [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/media/gpu/gpu_video_decode_accelerator_factory.h [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/media/gpu/ipc/service/gpu_video_decode_accelerator.cc [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/media/gpu/ipc/service/gpu_video_decode_accelerator.h [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/services/ui/gpu/gpu_service.cc [modify] https://crrev.com/beabb626561e9899cb3099b3c7cd5a1447bf00f7/services/ui/gpu/gpu_service.h
,
May 8 2017
This should be fixed in Canary.
,
May 18 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0fa9cda3c18d314dab4b971123f26cb5b9480344 commit 0fa9cda3c18d314dab4b971123f26cb5b9480344 Author: John Bauman <jbauman@chromium.org> Date: Thu May 18 23:50:13 2017 Make disabling accelerated VPX decoding a GPU driver bug workaround. This is currently a blacklist entry, which means that it's calculated in the browser and the resulting decision could be incorrect if the GPU process uses a different GPU from what the browser expects. If this is a GPU driver bug workaround entry then it'll be determined with more information in the GPU process. TBR=zmo@chromium.org BUG= 687004 , 712006 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Review-Url: https://codereview.chromium.org/2682723003 Cr-Original-Commit-Position: refs/heads/master@{#469513} Review-Url: https://codereview.chromium.org/2888233002 . Cr-Commit-Position: refs/branch-heads/3071@{#623} Cr-Branched-From: a106f0abbf69dad349d4aaf4bcc4f5d376dd2377-refs/heads/master@{#464641} [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/content/browser/gpu/compositor_util.cc [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/content/browser/gpu/gpu_data_manager_impl_private.cc [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/content/browser/gpu/gpu_data_manager_testing_arrays_and_structs_autogen.h [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/gpu/config/gpu_blacklist.cc [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/gpu/config/gpu_blacklist_unittest.cc [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/gpu/config/gpu_driver_bug_list.json [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/gpu/config/gpu_driver_bug_workaround_type.h [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/gpu/config/gpu_feature_type.h [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/gpu/config/software_rendering_list.json [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/gpu/ipc/service/gpu_channel_manager.cc [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/gpu/ipc/service/gpu_channel_manager.h [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/gpu/ipc/service/gpu_channel_test_common.cc [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/media/gpu/dxva_video_decode_accelerator_win.cc [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/media/gpu/dxva_video_decode_accelerator_win.h [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/media/gpu/gpu_video_decode_accelerator_factory.cc [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/media/gpu/gpu_video_decode_accelerator_factory.h [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/media/gpu/ipc/service/gpu_video_decode_accelerator.cc [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/media/gpu/ipc/service/gpu_video_decode_accelerator.h [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/services/ui/gpu/gpu_service.cc [modify] https://crrev.com/0fa9cda3c18d314dab4b971123f26cb5b9480344/services/ui/gpu/gpu_service.h
,
May 22 2017
please fix asap --- effecting our production environment |
||||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Jan 31 2017