Hardware acceleration is unavailable in case of an up-to-date AMD switchable system
Reported by
djnem...@outlook.com,
Nov 12 2016
|
|||||||
Issue descriptionChrome Version : 54.0.2840.99 m (x64) OS : Windows 10, x64, version 10.0.14393 Build 14393 CPU : Intel® Core™ i5-6200U GPU0 : AMD Radeon™ R7 M360 (dedicated) GPU1 : Intel® HD Graphics 520 (integrated) My system contains the two aforementioned GPUs, which are switchable using an application provided by AMD. I'm running Chrome on the integrated GPU only. The problem is that apparently, Chrome blacklists these GPUs, resulting in an unavailable hardware acceleration. This problem does not occur using Microsoft Edge 38.14393.0.0. All of my GPU drivers are up to date. The contents of chrome://gpu/ by default: see gpu_info_before.txt (attached) Note that Chrome correctly detects the two GPUs of my system, and it also correctly marks the integrated Intel (GPU1) as active. However, under 'Driver Information' it lists the driver of the dedicated AMD card (GPU0) instead, see driver vendor, version and date. It seems that the GPU diagnostics cannot be finished even after several minutes, see line 126 of gpu_info_before.txt. After I enable flag 'ignore-gpu-blacklist', contents of chrome://gpu/ change as follows: see gpu_info_after.txt (attached)
,
Nov 14 2016
,
Jan 10 2017
Hardware acceleration is still unavailable on the aforementioned device and OS using Chrome 55.0.2883.87 m (x64), unless enabling flag 'ignore-gpu-blacklist'. Only a line number changed slightly in one of the error messages I listed in my previous comment. [184:3428:0110/165908:ERROR:gpu_video_decode_accelerator.cc(365)] : HW video decode not available for profile 12 [184:3428:0110/165908:ERROR:mf_helpers.cc(12)] : Error in dxva_video_decode_accelerator_win.cc on line 1409 [184:3428:0110/165908:ERROR:mf_helpers.cc(12)] : Error in dxva_video_decode_accelerator_win.cc on line 604 I tried to reproduce this under Ubuntu 16.10. Hardware acceleration is available there even without ignoring the GPU blacklist, but probably this is only because Ubuntu doesn't recognize my configuration as an AMD switchable system, see the attached log (in fact, it doesn't recognize the dedicated AMD graphics card at all). Please note that I haven't installed additional drivers on Ubuntu, so most likely this is why Chromium doesn't recognize the dedicated GPU. However, I believe the fact that hardware acceleration is available in this case confirms that the source of the originally reported issue is related to improper handling of multi-GPU configurations.
,
Apr 8 2017
,
Apr 17 2017
Can you run this with --user-data-dir="some folder" and see with a clean start, weather you still have this issue?
,
May 28 2017
I have tried running Chrome with an empty user data directory using --user-data-dir="some empty directory", but the issue is still present. Before ignoring the GPU blacklist --------------------------------- Parameters: --user-data-dir="D:/data" chrome://gpu: empty_user_data_before.txt (attached) Errors (displayed in the Windows command line): [11164:8572:0528/081944.000:ERROR:browser_gpu_channel_host_factory.cc(125)] Failed to create channel. After ignoring the GPU blacklist -------------------------------- Parameters: --user-data-dir="D:/data" --ignore-gpu-blacklist chrome://gpu: empty_user_data_after.txt (attached) Errors (displayed in the log under chrome://gpu): [8148:11020:0528/082447.347:ERROR:mf_helpers.cc(12)] : Error in dxva_video_decode_accelerator_win.cc on line 1538 [8148:11020:0528/082447.347:ERROR:mf_helpers.cc(12)] : Error in dxva_video_decode_accelerator_win.cc on line 625 [8148:11020:0528/082447.348:ERROR:gpu_video_decode_accelerator.cc(375)] : HW video decode not available for profile vp9 profile0
,
May 28 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 1 2018
,
Jun 1 2018
This should have been fixed a while ago when I redo the blacklisting system. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by djnem...@outlook.com
, Nov 12 2016