New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 669658 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

WebGL completely broken on my Windows 10 PC with AMD video card (see details below)

Reported by an...@umiacs.umd.edu, Nov 29 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36

Steps to reproduce the problem:
1. Run any of the demos on the threejs website. WebGL fails to initialize
2. 
3. 

What is the expected behavior?
WebGL should work. It works on Firefox on my computer, including advanced features such as render-to-texture

What went wrong?
Not sure when this happened, but WebGL no longer works on my computer. Video card details:

Graphics Card Manufacturer - Powered by AMD
Graphics Chipset - AMD Radeon (TM) R9 M375X
Device ID - 6820
Vendor ID - 1002
SubSystem ID - 06DA
SubSystem Vendor ID - 1028
Revision ID - 83
Bus Type - PCI Express 3.0
Current Bus Settings - PCI Express 3.0 x16
BIOS Version - 015.048.000.069
BIOS Part Number - BR46630.001
BIOS Date - 2015/11/13 02:00
Memory Size - 2048 MB
Memory Type - GDDR5
Memory Clock - 1125 MHz
Core Clock - 925 MHz
Total Memory Bandwidth - 72 GByte/s

I've tried tinkering with the webgl flags as detailed in other posts about this topic, but nothing seems to help. Please help!

Did this work before? Yes Not sure

Does this work in other browsers? N/A

Chrome version: 54.0.2840.99  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0
 
I forgot to mention that I'm referring to WebGL not working on the latest version of Chrome. WebGL works fine in Firefox and (even) Edge. 
Components: Blink>WebGL
Labels: M-54
Thanks for the GPU information. Can you also save and attach the contents of your about:gpu page?

Comment 4 by kbr@chromium.org, Nov 30 2016

Note: plaintext from about:gpu is fine -- easier to read -- feel free to just copy/paste it here.

Here it is:

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 disabled
Video Decode: Software only, hardware acceleration unavailable
Video Encode: Software only, hardware acceleration unavailable
VPx Video Decode: Software only, hardware acceleration unavailable
WebGL: Unavailable
Driver Bug Workarounds
clear_uniforms_before_first_program_use
disable_d3d11
disable_discard_framebuffer
disable_dxgi_zero_copy_video
disable_nv12_dxgi_video
disable_framebuffer_cmaa
exit_on_context_lost
scalarize_vec_and_mat_constructor_args
Problems Detected
GPU process was unable to boot: GPU process launch failed.
Disabled Features: all
Some drivers are unable to reset the D3D device in the GPU process sandbox
Applied Workarounds: exit_on_context_lost
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
Framebuffer discarding can hurt performance on non-tilers: 570897
Applied Workarounds: disable_discard_framebuffer
NV12 DXGI video hangs or displays incorrect colors on AMD drivers: 623029, 644293
Applied Workarounds: disable_dxgi_zero_copy_video, disable_nv12_dxgi_video
Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198
Applied Workarounds: disable_framebuffer_cmaa
Accelerated rasterization has been disabled, either via blacklist, about:flags or the command line.
Disabled Features: rasterization
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers
Version Information
Data exported	11/30/2016, 9:32:43 AM
Chrome version	Chrome/54.0.2840.99
Operating system	Windows NT 10.0.14393
Software rendering list version	0
Driver bug list version	9.02
ANGLE commit id	905fbdea9ef0
2D graphics backend	Skia/54 a21f10dd8b19c6cb47d07d94d0a0525c16461969
Command Line Args	Files (x86)\Google\Chrome\Application\chrome.exe" --flag-switches-begin --enable-experimental-canvas-features --enable-unsafe-es3-apis --enable-webgl-draft-extensions --ignore-gpu-blacklist --flag-switches-end
Driver Information
Initialization time	0
In-process GPU	true
Sandboxed	false
GPU0	VENDOR = 0x1002, DEVICE= 0x6820
GPU1	VENDOR = 0x8086, DEVICE= 0x191d
Optimus	false
AMD switchable	true
Desktop compositing	Aero Glass
Diagonal Monitor Size of \\.\DISPLAY17	17.2"
Driver vendor	Advanced Micro Devices, Inc.
Driver version	21.19.137.1
Driver date	9-16-2016
Pixel shader version	
Vertex shader version	
Max. MSAA samples	
Machine model name	
Machine model version	
GL_VENDOR	
GL_RENDERER	
GL_VERSION	
GL_EXTENSIONS	
Disabled Extensions	
Window system binding vendor	
Window system binding version	
Window system binding extensions	
Direct rendering	Yes
Reset notification strategy	0x0000
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
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
[6868:9536:1126/141618:ERROR:gl_surface_egl.cc(252)] : No suitable EGL configs found.
[6868:9536:1126/141618:ERROR:gl_surface_egl.cc(1012)] : eglCreatePbufferSurface failed with error EGL_BAD_CONFIG
[6868:9536:1126/141618:ERROR:gpu_info_collector.cc(35)] : gl::GLContext::CreateOffscreenGLSurface failed
[6868:9536:1126/141618:ERROR:gpu_info_collector.cc(108)] : Could not create surface for info collection.
[6868:9536:1126/141618:ERROR:gpu_main.cc(506)] : gpu::CollectGraphicsInfo failed (fatal).
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
Cc: kbr@chromium.org zmo@chromium.org geoffl...@chromium.org
Components: Internals>GPU
Status: Untriaged (was: Unconfirmed)
Thanks. There's a couple odd things here - the Revision ID is missing from Chrome's about:gpu, which might or not matter. Your card (AMD Radeon™ R9 M375) should support D3D11, according to http://developer.amd.com/resources/ati-catalyst-pc-vendor-id-1002-li/, but we disable it because you're under an AMD+Intel swichable configuration. (Disable Direct3D11 on systems with AMD switchable graphics: 451420). I don't think we can easily turn on D3D11 for this. Then there's the reason why WebGL is failing: 

[6868:9536:1126/141618:ERROR:gl_surface_egl.cc(252)] : No suitable EGL configs found.

I'm not sure why we're getting that, but I seem to recall us running into this problem before. CC'ing some other folks.
I think this is likely that you're trying to enable WebGL 2 (--enable-unsafe-es3-apis is being used) on this system that doesn't support it (D3D11 blacklisted) and this version of Chrome didn't have the fallback from ES3 to ES2 contexts in place yet.

I suspect WebGL 1 will start working again if you remove the --enable-unsafe-es3-apis flag or update to Chrome 55.
ok thanks. I'm currently only concerned with having WebGL to work. I'm working on a simulation that renders some images on which I need to run image processing/computer vision algorithms. I'm want to use NaCl to call native OpenCV functions from the WebGL simulation, but stuck as I can't run WebGL at all in Chrome. No other browser provides the power and flexibility that chrome does in terms of being able to run native code through NaCL/pNaCl and combine that with WebGL all through Javascript. So love chrome, just need this issue to be fixed. Currently having to use firefox for the webgl work, which is far from ideal. Please let me know anything I can help with debugging this.
Updated to the latest chrome beta and webgl is working again. Thanks a lot guys!! 

Sign in to add a comment