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

Issue 656989 link

Starred by 32 users

Issue metadata

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

Restricted
  • Only users with EditIssue permission may comment.



Sign in to add a comment

WebGL not working with latest Chrome release Version 54.0.2840.59 m

Reported by timothy....@gmail.com, Oct 18 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.59 Safari/537.36

Example URL:
https://cesiumjs.org/NewYork/index.html & http://get.webgl.org/

Steps to reproduce the problem:
1. Visit https://cesiumjs.org/NewYork/index.html & receive the WebGL error RuntimeError: The browser supports WebGL, but initialization failed.
2. Visit the suggested http://get.webgl.org/ & see the message Hmm. While your browser seems to support WebGL, it is disabled or unavailable. If possible, please ensure that you are running the latest drivers for your video card.
3. I have checked 
chrome://settings - Use hardware acceleration when available is checked 
chrome://gpu/ - WebGL: Hardware accelerated
further details: 
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/chrome/XIy6dtJY4uo/4k_trkMXAwAJ

What is the expected behavior?
Expected behavior for https://cesiumjs.org/NewYork/index.html is a 3D rendering of NYC buildings with fly over and navigation. Similar to the video screen capture taken with Chrome, pre-update on 09/29/2016 : http://www.screencast.com/t/AeVRdi7YT

What went wrong?
WebGL doesn't work at all & it did before the latest Chrome update. See screen capture taken of Chrome running a WebGL application on 09/29/16:
http://www.screencast.com/t/AeVRdi7YT

Does it occur on multiple sites: Yes

Is it a problem with a plugin? N/A 

Did this work before? Yes Not sure what the version I had before I updated to Version 54.0.2840.59 m

Does this work in other browsers? Yes

Chrome version: 54.0.2840.59  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0

I have asked some in the geo community & others have received this same WebGL problem after Chrome version update.
 
Cc: kbr@chromium.org zmo@chromium.org ligim...@chromium.org bustamante@chromium.org
Components: -Blink Internals>GPU>WebGL
Labels: M-54 pre-stable-54.0.2840.59 Needs-Bisect
I've experienced this as well - been developing sites using WebGL in Chrome for two years on my machine, and suddenly last Saturday my GPU was irrevocably blacklisted. Tabs hang for a significant amount of time as well, but I wonder if that's because hardware acceleration fails.

OS: Windows 10 Pro build 14393
Chrome version: same as parent, also experienced on yesterday's Canary build
Hardware: Surface 2

Comment 3 by zmo@chromium.org, Oct 19 2016

Cc: geoffl...@chromium.org jmad...@chromium.org

Comment 4 by zmo@chromium.org, Oct 19 2016

We will need about:gpu content to know exact hardware/platform to further investigate
For sure. If there's a better format for me to share this with, just let me know:

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
Driver Bug Workarounds
clear_uniforms_before_first_program_use
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: GPU access is disabled in chrome://settings.
Disabled Features: all
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
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	10/19/2016, 10:02:22 AM
Chrome version	Chrome/54.0.2840.59
Operating system	Windows NT 10.0.14393
Software rendering list version	0
Driver bug list version	9.00
ANGLE commit id	905fbdea9ef0
2D graphics backend	Skia/54 a21f10dd8b19c6cb47d07d94d0a0525c16461969
Command Line Args	Files (x86)\Google\Chrome\Application\chrome.exe" --flag-switches-begin --ignore-gpu-blacklist --flag-switches-end
Driver Information
Initialization time	98
In-process GPU	false
Sandboxed	true
GPU0	VENDOR = 0x8086, DEVICE= 0x0a16
Optimus	false
AMD switchable	false
DisplayLink Version	8.0.629.0
Desktop compositing	Aero Glass
Diagonal Monitor Size of \\.\DISPLAY1	10.6"
Diagonal Monitor Size of \\.\DISPLAY3	23.9"
Diagonal Monitor Size of \\.\DISPLAY2	23.5"
Driver vendor	Intel Corporation
Driver version	20.19.15.4331
Driver date	11-18-2015
Pixel shader version	5.0
Vertex shader version	5.0
Max. MSAA samples	8
Machine model name	
Machine model version	
GL_VENDOR	Google Inc.
GL_RENDERER	ANGLE (Intel(R) HD Graphics Family Direct3D11 vs_5_0 ps_5_0)
GL_VERSION	OpenGL ES 2.0 (ANGLE 2.1.0.905fbdea9ef0)
GL_EXTENSIONS	GL_OES_element_index_uint GL_OES_packed_depth_stencil GL_OES_get_program_binary GL_OES_rgb8_rgba8 GL_EXT_texture_format_BGRA8888 GL_EXT_read_format_bgra GL_NV_pixel_buffer_object GL_OES_mapbuffer GL_EXT_map_buffer_range GL_EXT_color_buffer_half_float GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_float GL_OES_texture_float_linear GL_EXT_texture_rg GL_EXT_texture_compression_dxt1 GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_OES_compressed_ETC1_RGB8_texture GL_EXT_sRGB GL_ANGLE_depth_texture GL_OES_depth32 GL_EXT_texture_storage GL_OES_texture_npot GL_EXT_draw_buffers GL_EXT_texture_filter_anisotropic GL_EXT_occlusion_query_boolean GL_NV_fence GL_EXT_disjoint_timer_query GL_EXT_robustness GL_EXT_blend_minmax GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_pack_reverse_row_order GL_OES_standard_derivatives GL_EXT_shader_texture_lod GL_EXT_frag_depth GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_EXT_discard_framebuffer GL_EXT_debug_marker GL_OES_EGL_image GL_OES_EGL_image_external GL_NV_EGL_stream_consumer_external GL_EXT_unpack_subimage GL_NV_pack_subimage GL_OES_vertex_array_object GL_KHR_debug GL_ANGLE_lossy_etc_decode GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_sync_query GL_CHROMIUM_copy_texture
Disabled Extensions	
Window system binding vendor	Google Inc. (adapter LUID: 0000000000007dad)
Window system binding version	1.4 (ANGLE 2.1.0.905fbdea9ef0)
Window system binding extensions	EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_ANGLE_direct_composition 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_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_stream_producer_d3d_texture_nv12
Direct rendering	Yes
Reset notification strategy	0x8252
GPU process crash count	3
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
GpuProcessHostUIShim: The GPU process crashed!
GpuProcessHostUIShim: The GPU process crashed!
GpuProcessHostUIShim: The GPU process crashed!

Comment 6 by zmo@chromium.org, Oct 19 2016

It looks like GPU process crashed three times and GPU access got disabled.

If you restart the browser, you should get back GPU acceleration. Now the question is what WebGL app did you run to cause the crash.
My full chrome://gpu content is attached. 
Note, a colleague did a test with older 53 version on https://cesiumjs.org/NewYork/index.html then updated to 54 build and got the same error also attached.

Have heard from others that Chrome on Mac OSX WebGL is not failing, just on Windows, for me Win7


chrome-gpu-content.txt
81.0 KB View Download
Chrome-WebGL-error.PNG
46.3 KB View Download

Comment 8 by zmo@chromium.org, Oct 19 2016

 Issue 653135  has been merged into this issue.
@zmo, here's what I've tried:
Restarted the browser multiple times
Restarted the computer multiple times
Toggled and untoggled #ignore-gpu-blacklist flag
Updated video drivers
Uninstalled and reinstalled Chrome
Uninstalled Chrome and installed Chrome Canary instead
Applied latest Windows updates
It's not a specific app, any page using WebGL causes the failure.

Comment 10 by zmo@chromium.org, Oct 19 2016

I checked on my Windows machine with NVidia Quadro K2200 on Win 7, on M53, https://cesiumjs.org/NewYork/index.html works, then I upgrade Chrome to M54, it still works.  So I guess it's GPU specific issue.

Comment 11 by zmo@chromium.org, Oct 19 2016

timothy.morrissey@gmail.com: can you try running chrome with --disable_chromium_framebuffer_multisample and see if you can get the https://cesiumjs.org/NewYork/index.html to run again? Note it's "_" in the switch, not "-"
Cc: krajshree@chromium.org
Labels: Needs-Feedback
Retested the issue on Windows 10 using chrome reported version #54.0.2840.59 and latest canary #56.0.2895.0 as per the comment #0.

Observed that the issue is not reproducible.

Attaching screencast for the same.

Reporter@ - Could you please check this issue on latest canary #56.0.2895.0 as per comment #11 by creating a new profile without any apps and extensions and please let us know if the issue persist or not.
656989.mp4
6.6 MB View Download

Comment 13 by eno...@onshape.com, Oct 20 2016

We've been getting reports of users on Windows who are failing to get a valid WebGL context.  chrome://gpu reports hardware accelerated WebGL, however no page can create a valid context (including get.webgl.org and cad.onshape.com).  

GPUs that we've seen reproduce this so far are a GeForce 9600M GT and GeForce 8500 GT, one known to be on Chrome 54.0.2840.59.
Over in  bug #653135 , there's also a report for the GeForce GTX 260 GPU for Chrome v54.0.2840.59 on Windows 10 with bold older and latest GPU drivers. I've posted an about:gpu output there for the WebGL issue.

This bug may also be the reason for me having problems when hovering and playing videos on Facebook. In the same period that I've been experiencing the WebGL issue, I often get about two seconds of black screen (I suspect it's the graphics driver restarting) or a crash of my NVidia driver showing a dialog box asking me if I want to open the NVidia support forum. I'm attaching about:gpu for one of those crashes here. I could easily reproduce the error by starting Chrome, going to a FB page of a friend who has videos and pressing play on one of them. Boom.
gpu.html
160 KB View Download
Retested my Surface 2 on version 56.0.2896.0 canary (64-bit) this morning with no success, using the method krajshree detailed.

Coincidentally, my Surface 1 at home was blacklisted when it updated to v54 last night, but I was able to use --ignore-gpu-blacklist to get WebGL working again. Have there been changes to the GPU blacklist recently? How do GPUs get blacklisted? Everything I can find on the web points to machines older than 2009 being placed on the blacklist, but that's not the case in this situation.
>>can you try running chrome with --disable_chromium_framebuffer_multisample and see if you can get the https://cesiumjs.org/NewYork/index.html to run again? Note it's "_" in the switch, not "-";

This works for me !

Attached pdf with gpu info WITHOUT "--disable_chromium_framebuffer_multisample" key
chrome___gpu for GTS 250.pdf
139 KB Download

Comment 17 by zmo@chromium.org, Oct 21 2016

Cc: cwallez@chromium.org
Owner: geoffl...@chromium.org
Status: Assigned (was: Unconfirmed)
@geofflang: it seems the multisampled path is somehow changed between M53 and M54 and now we get the OUT_OF_MEMORY error on framebufferRenderbufferMultisamle(). I am not sure if it's from ANGLE or from the driver. Can you take a further dig?
I wasn't able to repro this on any of the cards in house.  Going to pick up a GTS 250/260 since there are at least two reports with that card.
Running chrome.exe --disable_chromium_framebuffer_multisample did fix the issue and I am able to hit https://cesiumjs.org/NewYork/index.html without an error. 

Is this the workaround or a permanent solution for this? When could I expect a new Chrome version that doesn't require this flag?

Thanks,
Tim Morrissey
We still haven't reproduced this in house so I can't give an estimate yet.  Once I can make a targeted fix, you will no longer need the flag.

Comment 21 by ftrip...@gmail.com, Oct 25 2016

Just to give my info; Just noticed that the latest Chrome (54.0.2840.71 m) is not supporting my viewer in WebGL anymore. I noticed this on one desktop (GeForce 9800GT) which already had the latest version, checked another desktop (GeForce 8500GT), still on Chrome 53 and there it worked. Then it automatically updated to Chrome 54 and it stopped working.
My app is based on krpano, testing links can be found on:
http://krpano.com/docu/html5/

Seems pretty clear that the issue is for DirectX 10.0 level cards only.  I should have one to test with in a couple days.

Comment 23 by mroe...@gmail.com, Oct 26 2016

Can confirm the issue with an older GeForce 9600GT also. And that the suggested flag indeed fixes the issue.
The --disable_chromium_framebuffer_multisample does indeed fix the WebGL issue but it doesn't fix the problem I described in Comment #14 where the NVidia driver crashes when playing videos. I'll post new contents of about:gpu as it looks now with --disable_chromium_framebuffer_multisample.
gpu.html
150 KB View Download
The --disable_chromium_framebuffer_multisample worked for one of our customers as well.
Cc: brajkumar@chromium.org
 Issue 633896  has been merged into this issue.
Can confirm for a GeForce 9800GT and a GTX260. The former happened in August, so it must be an older change that caused it (perhaps the difference being the amount of memory these two cards have).

Coming from  issue 633896 .
 Issue 660642  has been merged into this issue.
Cc: sande...@chromium.org pucchakayala@chromium.org ddorwin@chromium.org pbomm...@chromium.org
 Issue 654164  has been merged into this issue.
Labels: ReleaseBlock-Stable
Adding RB label for tracking purpose.
Labels: -Needs-Feedback -M-54 -Needs-Bisect M-55
M54 Stable is already deployed today,we should target to M55.

Comment 32 by avi...@gmail.com, Nov 2 2016

I am facing similar issue where no webGL content seems to be working. We are developing on unity webGL and I seem to be only one to reproduce the issue although others may be having similar setup as I do.

I have a Dell laptop with dell USB dock (DisplayLink). 

When trying unity demo (beta.unity3d.com/jonas/AngryBots/), I am suggested to use firefox to show webGL content.

I just noticed that if I do not have the DisplayLink connected and restart chrome, it starts working. And if I have chrome already up and running (with webGL working) and connect DisplayLink, webGL content keeps working.

Attached files have chrome://gpu page with and without display link connected. You can also find additional info about Chrome and windows versions in there.

Issue appeared after updating chrome to version 54.
gpu_html_with_displaylink_webGL_not_working.html
48.8 KB View Download
gpu_html_without_displaylink_webGL_working.html
151 KB View Download
aviita: Your issue is not the same as the others, Chrome is failing to detect the GPU and disabling all GPU acceleration.  Can you please file another bug for that?

Comment 34 Deleted

Not sure if the new M54-Stable is supposed to fix it, but it doesn't in my case (GeForce 9800GT, on Windows 10, with Chromium Version 54.0.2840.87 m (64-bit))

The switch --disable_chromium_framebuffer_multisample DOES work of course

Thanks.
I can also confirm that the update to the 54.0.2840.87 m version from the 54.0.2840.59 version still produces the same WebGL issues as before. See initial posting or Comment 7 above for specs. https://bugs.chromium.org/p/chromium/issues/detail?id=656989#c7

Using the --disable_chromium_framebuffer_multisample flag does still fix the issue with the new version update.

Thanks for the help.
Labels: -Pri-2 Pri-1
(kbr posting as pbommana from his machine)

The failure to allocate multisampled renderbuffers on older (ps_4_0?) GPUs is reproducible, and is affecting other web sites that probe WebGL's presence, including Bank of America's site.

Raising to P1. This is a stable release blocker, even if just to add a blacklist entry for these older GPUs. Ideally we would figure out what is failing in ANGLE.

Here is about:gpu from the affected machine. Note the call to glRenderbufferStorageMultisampleCHROMIUM failing with GL_OUT_OF_MEMORY, causing the GPU process to exit.

----------

Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Rasterization: Software only, hardware acceleration unavailable
Video Decode: Hardware accelerated
Video Encode: Hardware accelerated
VPx Video Decode: Software only, hardware acceleration unavailable
WebGL: Hardware accelerated
Driver Bug Workarounds
clear_uniforms_before_first_program_use
disable_direct_composition
disable_discard_framebuffer
disable_dxgi_zero_copy_video
disable_framebuffer_cmaa
exit_on_context_lost
force_cube_complete
scalarize_vec_and_mat_constructor_args
texsubimage_faster_than_teximage
Problems Detected
VPx decoding isn't supported before Windows 10 anniversary update.: 616318
Disabled Features: accelerated_vpx_decode
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
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
ANGLE crash on glReadPixels from incomplete cube map texture: 518889
Applied Workarounds: force_cube_complete
Framebuffer discarding can hurt performance on non-tilers: 570897
Applied Workarounds: disable_discard_framebuffer
Direct composition flashes black initially on Win <10: 588588
Applied Workarounds: disable_direct_composition
Zero copy DXGI video hangs on shutdown on Win < 8.1: 621190
Applied Workarounds: disable_dxgi_zero_copy_video
Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198
Applied Workarounds: disable_framebuffer_cmaa
Zero-copy NV12 video displays incorrect colors on NVIDIA drivers.: 635319
Applied Workarounds: disable_dxgi_zero_copy_video
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers
Version Information
Data exported	11/2/2016, 5:03:23 PM
Chrome version	Chrome/55.0.2883.35
Operating system	Windows NT 6.1.7601 SP1
Software rendering list version	11.16
Driver bug list version	9.13
ANGLE commit id	4e5f1451372b
2D graphics backend	Skia/55 d82029915640515b5a4c9561bcc6a202a4e6e0e7
Command Line Args	Files (x86)\Google\Chrome\Application\chrome.exe" --flag-switches-begin --flag-switches-end
Driver Information
Initialization time	57
In-process GPU	false
Sandboxed	false
GPU0	VENDOR = 0x10de, DEVICE= 0x0659
Optimus	false
AMD switchable	false
Desktop compositing	Aero Glass
Diagonal Monitor Size of \\.\DISPLAY2	24.0"
Diagonal Monitor Size of \\.\DISPLAY1	24.0"
Driver vendor	NVIDIA
Driver version	9.18.13.2086
Driver date	8-30-2013
Pixel shader version	4.0
Vertex shader version	4.0
Max. MSAA samples	8
Machine model name	
Machine model version	
GL_VENDOR	Google Inc.
GL_RENDERER	ANGLE (NVIDIA Quadro FX 580 Direct3D11 vs_4_0 ps_4_0)
GL_VERSION	OpenGL ES 2.0 (ANGLE 2.1.0.4e5f1451372b)
GL_EXTENSIONS	GL_ANGLE_depth_texture GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode 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_copy_texture GL_CHROMIUM_sync_query GL_EXT_blend_minmax GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_frag_depth GL_EXT_map_buffer_range GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_dxt1 GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_mapbuffer 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: 000000000000eccb)
Window system binding version	1.4 (ANGLE 2.1.0.4e5f1451372b)
Window system binding extensions	EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation 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_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv 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
0
b3DAccelerationEnabled	true
b3DAccelerationExists	true
bAGPEnabled	true
bAGPExistenceValid	true
bAGPExists	true
bCanRenderWindow	true
bDDAccelerationEnabled	true
bDriverBeta	false
bDriverDebug	false
bDriverSigned	false
bDriverSignedValid	false
bNoHardware	false
dwBpp	32
dwDDIVersion	10
dwHeight	1200
dwRefreshRate	59
dwWHQLLevel	0
dwWidth	1920
iAdapter	1
lDriverSize	15154704
lMiniVddSize	0
szAGPStatusEnglish	Enabled
szAGPStatusLocalized	Enabled
szChipType	Quadro FX 580
szD3DStatusEnglish	Enabled
szD3DStatusLocalized	Enabled
szDACType	Integrated RAMDAC
szDDIVersionEnglish	10
szDDIVersionLocalized	10
szDDStatusEnglish	Enabled
szDDStatusLocalized	Enabled
szDXVAHDEnglish	Supported
szDXVAModes	ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
szDescription	NVIDIA Quadro FX 580
szDeviceId	0x0659
szDeviceIdentifier	{D7B71E3E-4519-11CF-487B-37261CC2C435}
szDeviceName	\\.\DISPLAY1
szDisplayMemoryEnglish	4071 MB
szDisplayMemoryLocalized	4071 MB
szDisplayModeEnglish	1920 x 1200 (32 bit) (59Hz)
szDisplayModeLocalized	1920 x 1200 (32 bit) (59Hz)
szDriverAssemblyVersion	9.18.13.2086
szDriverAttributes	Final Retail
szDriverDateEnglish	8/30/2013 15:26:08
szDriverDateLocalized	8/30/2013 3:26:08 PM
szDriverLanguageEnglish	English
szDriverLanguageLocalized	English
szDriverModelEnglish	WDDM 1.1
szDriverModelLocalized	WDDM 1.1
szDriverName	nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
szDriverNodeStrongName	oem41.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section020:9.18.13.2086:pci\ven_10de&dev_0659
szDriverSignDate	
szDriverVersion	9.18.0013.2086
szKeyDeviceID	Enum\PCI\VEN_10DE&DEV_0659&SUBSYS_063A10DE&REV_A1
szKeyDeviceKey	\Registry\Machine\System\CurrentControlSet\Control\Video\{2CCA85BB-FEDC-4A18-9AD1-C19DA1083E20}\0000
szManufacturer	NVIDIA
szMiniVdd	n/a
szMiniVddDateEnglish	n/a
szMiniVddDateLocalized	n/a
szMonitorMaxRes	
szMonitorName	Generic PnP Monitor
szNotesEnglish	No problems found.
szNotesLocalized	No problems found.
szOverlayEnglish	Supported
szRankOfInstalledDriver	00E02001
szRegHelpText	
szRevision	
szRevisionId	0x00A1
szSubSysId	0x063A10DE
szTestResultD3D7English	Not run
szTestResultD3D7Localized	Not run
szTestResultD3D8English	Not run
szTestResultD3D8Localized	Not run
szTestResultD3D9English	Not run
szTestResultD3D9Localized	Not run
szTestResultDDEnglish	Not run
szTestResultDDLocalized	Not run
szVdd	n/a
szVendorId	0x10DE
1
b3DAccelerationEnabled	true
b3DAccelerationExists	true
bAGPEnabled	true
bAGPExistenceValid	true
bAGPExists	true
bCanRenderWindow	true
bDDAccelerationEnabled	true
bDriverBeta	false
bDriverDebug	false
bDriverSigned	false
bDriverSignedValid	false
bNoHardware	false
dwBpp	32
dwDDIVersion	10
dwHeight	1200
dwRefreshRate	59
dwWHQLLevel	0
dwWidth	1920
iAdapter	0
lDriverSize	15154704
lMiniVddSize	0
szAGPStatusEnglish	Enabled
szAGPStatusLocalized	Enabled
szChipType	Quadro FX 580
szD3DStatusEnglish	Enabled
szD3DStatusLocalized	Enabled
szDACType	Integrated RAMDAC
szDDIVersionEnglish	10
szDDIVersionLocalized	10
szDDStatusEnglish	Enabled
szDDStatusLocalized	Enabled
szDXVAHDEnglish	Supported
szDXVAModes	ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
szDescription	NVIDIA Quadro FX 580
szDeviceId	0x0659
szDeviceIdentifier	{D7B71E3E-4519-11CF-487B-37261CC2C435}
szDeviceName	\\.\DISPLAY2
szDisplayMemoryEnglish	4071 MB
szDisplayMemoryLocalized	4071 MB
szDisplayModeEnglish	1920 x 1200 (32 bit) (59Hz)
szDisplayModeLocalized	1920 x 1200 (32 bit) (59Hz)
szDriverAssemblyVersion	9.18.13.2086
szDriverAttributes	Final Retail
szDriverDateEnglish	8/30/2013 15:26:08
szDriverDateLocalized	8/30/2013 3:26:08 PM
szDriverLanguageEnglish	English
szDriverLanguageLocalized	English
szDriverModelEnglish	WDDM 1.1
szDriverModelLocalized	WDDM 1.1
szDriverName	nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
szDriverNodeStrongName	oem41.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section020:9.18.13.2086:pci\ven_10de&dev_0659
szDriverSignDate	
szDriverVersion	9.18.0013.2086
szKeyDeviceID	Enum\PCI\VEN_10DE&DEV_0659&SUBSYS_063A10DE&REV_A1
szKeyDeviceKey	\Registry\Machine\System\CurrentControlSet\Control\Video\{2CCA85BB-FEDC-4A18-9AD1-C19DA1083E20}\0001
szManufacturer	NVIDIA
szMiniVdd	n/a
szMiniVddDateEnglish	n/a
szMiniVddDateLocalized	n/a
szMonitorMaxRes	
szMonitorName	Generic PnP Monitor
szNotesEnglish	No problems found.
szNotesLocalized	No problems found.
szOverlayEnglish	Supported
szRankOfInstalledDriver	00E02001
szRegHelpText	
szRevision	
szRevisionId	0x00A1
szSubSysId	0x063A10DE
szTestResultD3D7English	Not run
szTestResultD3D7Localized	Not run
szTestResultD3D8English	Not run
szTestResultD3D8Localized	Not run
szTestResultD3D9English	Not run
szTestResultD3D9Localized	Not run
szTestResultDDEnglish	Not run
szTestResultDDLocalized	Not run
szVdd	n/a
szVendorId	0x10DE
Log Messages
[4240:7200:1102/170317:ERROR:gles2_cmd_decoder.cc(7929)] : [.Offscreen-For-WebGL-0000000004566E60]GL ERROR :GL_OUT_OF_MEMORY : glRenderbufferStorageMultisampleCHROMIUM:
[4240:7200:1102/170317:ERROR:gles2_cmd_decoder.cc(7155)] : [.Offscreen-For-WebGL-0000000004566E60]GL ERROR :GL_OUT_OF_MEMORY : glFramebufferRenderbuffer:
[4240:7200:1102/170317:ERROR:gles2_cmd_decoder.cc(7155)] : [.Offscreen-For-WebGL-0000000004566E60]GL ERROR :GL_OUT_OF_MEMORY : glFramebufferRenderbuffer:
[4240:7200:1102/170317:ERROR:gles2_cmd_decoder.cc(14890)] : Offscreen context lost via ARB/EXT_robustness. Reset status = GL_UNKNOWN_CONTEXT_RESET_KHR
[4240:7200:1102/170317:ERROR:gles2_cmd_decoder.cc(4102)] : GLES2DecoderImpl: Context reset detected after MakeCurrent.
[4240:7200:1102/170317:ERROR:gpu_channel_manager.cc(224)] : Exiting GPU process because some drivers cannot recover from problems.
[4240:7200:1102/170317:ERROR:gpu_channel_manager.cc(224)] : Exiting GPU process because some drivers cannot recover from problems.
[4240:7200:1102/170317:ERROR:gpu_channel_manager.cc(224)] : Exiting GPU process because some drivers cannot recover from problems.
[4240:7200:1102/170317:ERROR:gpu_channel_manager.cc(224)] : Exiting GPU process because some drivers cannot recover from problems.
[4240:7200:1102/170317:ERROR:gpu_channel_manager.cc(224)] : Exiting GPU process because some drivers cannot recover from problems.
[4240:7200:1102/170317:ERROR:gpu_channel_manager.cc(224)] : Exiting GPU process because some drivers cannot recover from problems.
[4240:7200:1102/170317:ERROR:gpu_channel_manager.cc(224)] : Exiting GPU process because some drivers cannot recover from problems.
[4240:7200:1102/170317:ERROR:gpu_channel_manager.cc(224)] : Exiting GPU process because some drivers cannot recover from problems.
[4240:7200:1102/170317:ERROR:gpu_channel_manager.cc(224)] : Exiting GPU process because some drivers cannot recover from problems.
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.

(kbr posting as pbommana)

I can build Windows binaries to run on Prudhvi's machine; please tell me if I can help by adding error logging or similar, if you can't reproduce this yet.

Comment 39 by avi...@gmail.com, Nov 3 2016

geoffl... I created a separate bug for my problem.

 Issue 661930  - WebGL not working with DisplayLink
https://bugs.chromium.org/p/chromium/issues/detail?id=661930

**** Bulk edit -  please ignore if not applicable ****

A friendly reminder that M55 Stable is launch is coming soon! Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch ASAP so it gets enough baking time in Beta (before Stable promotion). Thank you!

Also due to Thanksgiving holidays in US, please make sure all fixes are ready and merged to M55 latest by 5:00 PM PT Friday, 11/18/16.
Project Member

Comment 41 by bugdroid1@chromium.org, Nov 7 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/angle/angle/+/62a90cf67d40a20c27a99094ab9f024b9206e38c

commit 62a90cf67d40a20c27a99094ab9f024b9206e38c
Author: Geoff Lang <geofflang@chromium.org>
Date: Mon Nov 07 16:01:17 2016

Don't use the bind SRV flag for MS textures in D3D11 FL 10.0.

With the latest Windows SDKs, it is an error to create a multisampled
texture with both bind SRV and DSV flags in feature level 10.0.  The
error:

D3D11 ERROR: ID3D11Device::CreateTexture2D: If the feature level is less
than D3D_FEATURE_LEVEL_10_1, a Texture2D with sample count > 1 cannot have
both D3D11_BIND_DEPTH_STENCIL and D3D11_BIND_SHADER_RESOURCE. This call may
appear to incorrectly return success on older/current D3D runtimes due to
missing validation, despite this debug layer message.
[STATE_CREATION ERROR #99: CREATETEXTURE2D_INVALIDBINDFLAGS]

BUG= 656989 

Change-Id: Iedce65f6c877786e28b96c159abd7a5b2a32cfd5
Reviewed-on: https://chromium-review.googlesource.com/408339
Reviewed-by: Geoff Lang <geofflang@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>

[modify] https://crrev.com/62a90cf67d40a20c27a99094ab9f024b9206e38c/src/libANGLE/renderer/d3d/d3d11/Renderer11.cpp
[modify] https://crrev.com/62a90cf67d40a20c27a99094ab9f024b9206e38c/src/libANGLE/renderer/d3d/d3d11/Blit11.cpp

Project Member

Comment 42 by bugdroid1@chromium.org, Nov 8 2016

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

commit 187ca2e7ff269eeebbc4710b45221e516907957c
Author: geofflang <geofflang@chromium.org>
Date: Tue Nov 08 01:34:55 2016

Roll ANGLE f097e23..01a80ee

https://chromium.googlesource.com/angle/angle.git/+log/f097e23..01a80ee

BUG= 656989 

TBR=jmadill@chromium.org

TEST=bots

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2488433002
Cr-Commit-Position: refs/heads/master@{#430467}

[modify] https://crrev.com/187ca2e7ff269eeebbc4710b45221e516907957c/DEPS

This is fixed on latest Chrome canary i.e., 56.0.2914.1 I am not seen WebGl rash anymore when visited the websites like "bankofamerica.com, Techcrunch.com" on my machine.

Comment 44 by kbr@chromium.org, Nov 10 2016

Labels: Merge-Request-55
Thanks Prudhvi for verifying!

Let me request merge back to M55.

Comment 45 by dimu@chromium.org, Nov 10 2016

Labels: -Merge-Request-55 Merge-Review-55 Hotlist-Merge-Review
[Automated comment] DEPS changes referenced in bugdroid comments, needs manual review.
Labels: -Merge-Review-55 Merge-Approved-55
Approving merge to M55 branch 2883 based on comment #43 and #44. Please merge ASAP.Thank you.
Project Member

Comment 47 by bugdroid1@chromium.org, Nov 10 2016

Labels: -merge-approved-55 merge-merged-2883
The following revision refers to this bug:
  https://chromium.googlesource.com/angle/angle/+/4d208abb1926e74c6ef886a8d5a01d12c267e3cf

commit 4d208abb1926e74c6ef886a8d5a01d12c267e3cf
Author: Geoff Lang <geofflang@chromium.org>
Date: Thu Nov 10 18:33:06 2016

Don't use the bind SRV flag for MS textures in D3D11 FL 10.0.

With the latest Windows SDKs, it is an error to create a multisampled
texture with both bind SRV and DSV flags in feature level 10.0.  The
error:

D3D11 ERROR: ID3D11Device::CreateTexture2D: If the feature level is less
than D3D_FEATURE_LEVEL_10_1, a Texture2D with sample count > 1 cannot have
both D3D11_BIND_DEPTH_STENCIL and D3D11_BIND_SHADER_RESOURCE. This call may
appear to incorrectly return success on older/current D3D runtimes due to
missing validation, despite this debug layer message.
[STATE_CREATION ERROR #99: CREATETEXTURE2D_INVALIDBINDFLAGS]

BUG= 656989 

Change-Id: Ife7d206f0b815b81558b084f05eca63bd85d8c75
Reviewed-on: https://chromium-review.googlesource.com/409695
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>

[modify] https://crrev.com/4d208abb1926e74c6ef886a8d5a01d12c267e3cf/src/libANGLE/renderer/d3d/d3d11/Renderer11.cpp
[modify] https://crrev.com/4d208abb1926e74c6ef886a8d5a01d12c267e3cf/src/libANGLE/renderer/d3d/d3d11/Blit11.cpp

Status: Fixed (was: Assigned)
I recently had a partition crash , had to reinstall OSX 10.10. Then suddenly chrome stopped enabling webgl. Firefox is ok. 


I had to go into the flags and enable this ? 

"Override software rendering list"

Comment 50 by zmo@chromium.org, Jan 20 2017

@#49, can you provide about:gpu where WebGL is disabled?
WebGL still doesnt work on 3 of our machines (2 OSX, 1 Windows 10). Details for one of them: OSX (10.11.6), Intel i7, chrome 56.0.2924.87. about:gpu is attached.

gpu.htm
47.5 KB View Download

Comment 52 by yang...@intel.com, Feb 27 2017

The GPU used is "AMD Radeon HD 6490M OpenGL Engine". BTW, the integrated GPU is Gen6 (SandyBridge), which is a bit old (year 2011). 

Comment 53 by kbr@chromium.org, Feb 27 2017

Labels: Restrict-AddIssueComment-EditIssue
#51, #52: this dual-GPU laptop contains an Intel HD 3000, and Chrome has blacklisted all acceleration functionality (including WebGL) on this GPU type because it was causing a large number of GPU process crashes. This was covered by Issue 592130 (restricted view, sorry).

This bug covers a specific issue on Windows. Closing this bug to further comments. Please file a new bug if you see problems in Chrome's WebGL implementation and include about:gpu.

Components: -Internals>GPU>WebGL Blink>WebGL

Sign in to add a comment