WebGL not working in latest Windows version (AMD switchable)
Reported by
pablocri...@gmail.com,
Apr 16 2017
|
|||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3067.6 Safari/537.36 Steps to reproduce the problem: Open a WebGL webpage like Google Maps What is the expected behavior? Maps will show a 3D map of the area What went wrong? Instead, it shows a basic version as OpenGL is not working, it used to work before the Creators Update of Windows Did this work before? Yes Before windows update Chrome version: 59.0.3067.6 Channel: dev OS Version: 10.0 Flash Version: Shockwave Flash 25.0 r0 With the latest Windows update webgl has stopped working due to a problem with my graphics card, if I enable Override software rendering list flag it will start working again, but in that case exit confirmation dialog in some webpages like Google Play Music will not show, making that trying to close that window will lead into a the browser not responding as there is no way to close that window
,
Apr 18 2017
Unable to reproduce the issue on the latest stable(57.0.2987.133) and the latest Dev(59.0.3067.6) on Windows 10 creator version: 1703(OS Build 15063.138). Driver: NVIDIA Quadro 400 Direct3D11 vs_4_1 ps_4_1. This is probably driver specific. pablocriadoalbillos@: Could you please attach the chrome://gpu details for further investigation.
,
Apr 19 2017
I attach both screenshots, with and without Override software rendering list flag enabled, and then the whole page with flag disabled. I'm using an Intel HD integrated graphics card together with a radeon dedicated card
,
Apr 19 2017
Thank you for providing more feedback. Adding requester "ajha@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 20 2017
I attach two screenshots, one with flag enabled and one without it, with the flag opengl works and so does 3d terrain.
,
Apr 20 2017
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 20 2017
Likely culprits seem to be: * GPU rasterization should only be enabled on NVIDIA and Intel DX11+, and AMD RX-R2 GPUs for now. Issue 643850 * Disable Direct3D11 on systems with AMD switchable graphics. Issue 451420 I don't think either of these is supposed to disable WebGL, though. We'll try to reproduce this. (Unmarking as a "regression" because the change was due to a change in system version, not chrome version, AFAIK.)
,
Apr 20 2017
-sandeepkumars +Internals>GPU>ANGLE, +jmadill I suspect the issue here is this: 1. D3D11 is disabled on AMD switchable. 2. I hear ANGLE may be failing to initialize the D3D9 backend after the creator's update? 3. This results in fallback to SwiftShader. 4. Google Maps is probably specifically blacklisting SwiftShader for performance reasons. However there is another ongoing issue on AMD switchable: issue 669382
,
Apr 20 2017
#9.4: Correct, Google Maps uses the failIfMajorPerformanceCaveat WebGL context creation flag.
,
Apr 28 2017
What would be the appropriate next step here?
,
May 3 2017
I'm having this very same issue. Running on Dell Inspiron 15 with Intel 5500 graphics with AMD R7 M260. If you uninstall AMD drivers it works.
,
May 3 2017
Let me grab this if jmadill doesn't mind?
,
May 10 2017
The latest canary should have this fixed, thanks to jbauman. Could someone test and verify this?
,
May 11 2017
Google maps and other webGL websites seem to be working correctly in latest canary, not in dev yet
,
May 11 2017
It will hit dev soon. Thanks for verifying.
,
May 16 2017
Just tested with Vysor extension ( https://www.vysor.io/ ) and it worked as well.
,
May 16 2017
jbauman: do we want to merge this back to earlier branch?
,
May 16 2017
,
May 17 2017
Your change meets the bar and is auto-approved for M59. Please go ahead and merge the CL to branch 3071 manually. Please contact milestone owner if you have questions. Owners: amineer@(Android), cmasso@(iOS), gkihumba@(ChromeOS), Abdul Syed@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
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
,
Jun 20 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Apr 17 2017