New issue
Advanced search Search tips

Issue 695215 link

Starred by 2 users

Issue metadata

Status: Duplicate
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

WebGL and WebGL2 disabled

Reported by carlos.a...@gmail.com, Feb 22 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. go to http://cabbibo.com/
2. It will show a compatibility error that WebGL is missing or not supported

What is the expected behavior?
The content will display and I will be able to interact with it. 

What went wrong?
Page WebGL content doesn't display (but the sound of the page plays properly). Other pages do not display content at all. 

Did this work before? Yes 52  or 53

Chrome version: 56.0.2924.87  Channel: stable
OS Version: OS X 10.10.5
Flash Version: Shockwave Flash 24.0 r0

Went to https://get.webgl.org/https://get.webgl.org/
and got the following 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

Went to chrome://gpu
Got the following result:

WebGL unavailable
WebGL2 unavailable

This works in Firefox Nightly 54.0 alpha

 

Comment 1 by ajha@chromium.org, Feb 23 2017

Components: Blink>WebGL
Labels: Needs-Bisect Needs-Triage-M56
Labels: -Needs-Triage-M56 Needs-Feedback
Your Mac OS version is very old. If you update, it is likely to fix the problem.

Could you also please paste the contents of chrome://gpu? Thanks.
As requested, If I need to attach it as PDF 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 unavailable
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
add_and_true_to_loop_condition
adjust_src_dst_region_for_blitframebuffer
decode_encode_srgb_for_generatemipmap
disable_av_sample_buffer_display_layer
disable_framebuffer_cmaa
disable_multimonitor_multisampling
disable_webgl_rgb_multisampling_usage
emulate_abs_int_function
get_frag_data_info_bug
init_one_cube_map_level_before_copyteximage
msaa_is_slow
pack_parameters_workaround_with_pack_buffer
rebind_transform_feedback_before_resume
regenerate_struct_names
remove_invariant_and_centroid_for_essl3
reset_base_mipmap_level_before_texstorage
rewrite_do_while_loops
rewrite_texelfetchoffset_to_texelfetch
scalarize_vec_and_mat_constructor_args
set_zero_level_before_generating_mipmap
unfold_short_circuit_as_ternary_operation
unpack_alignment_workaround_with_unpack_buffer
unpack_image_height_workaround_with_unpack_buffer
use_intermediary_for_copy_texture_image
use_shadowed_tex_level_params
use_unused_standard_shared_blocks
Problems Detected
GPU process was unable to boot: All GPU features are blacklisted.
Disabled Features: all
Intel HD 3000 driver crashes frequently on Mac: 592130
Disabled Features: all
Some GPUs on Mac can perform poorly with GPU rasterization. Disable all known Intel GPUs other than Intel 6th and 7th Generation cards, which have been tested.: 613272, 614468
Disabled Features: gpu_rasterization
Some GPUs on Mac can perform poorly with GPU rasterization. Disable all known AMD GPUs other than the R200, R300, and D series, which have been tested.: 613272, 614468
Disabled Features: gpu_rasterization
Multisampling is buggy on OSX when multiple monitors are connected: 237931
Applied Workarounds: disable_multimonitor_multisampling
Unfold short circuit on Mac OS X: 307751
Applied Workarounds: unfold_short_circuit_as_ternary_operation
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
Mac drivers handle struct scopes incorrectly: 403957
Applied Workarounds: regenerate_struct_names
On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
Applied Workarounds: msaa_is_slow
glGenerateMipmap fails if the zero texture level is not set on some Mac drivers: 560499
Applied Workarounds: set_zero_level_before_generating_mipmap
Pack parameters work incorrectly with pack buffer bound: 563714
Applied Workarounds: pack_parameters_workaround_with_pack_buffer
Alignment works incorrectly with unpack buffer bound: 563714
Applied Workarounds: unpack_alignment_workaround_with_unpack_buffer
copyTexImage2D fails when reading from IOSurface on multiple GPU types.: 581777
Applied Workarounds: use_intermediary_for_copy_texture_image
Multisample renderbuffers with format GL_RGB8 have performance issues on Intel GPUs.: 607130
Applied Workarounds: disable_webgl_rgb_multisampling_usage
Mac Drivers store texture level parameters on int16_t that overflow: 610153
Applied Workarounds: use_shadowed_tex_level_params
Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198
Applied Workarounds: disable_framebuffer_cmaa
glGetFragData{Location|Index} works incorrectly on Max: 638340
Applied Workarounds: get_frag_data_info_bug
glResumeTransformFeedback works incorrectly on Intel GPUs: 638514
Applied Workarounds: rebind_transform_feedback_before_resume
glTexStorage* are buggy when base mipmap level is not 0: 640506
Applied Workarounds: reset_base_mipmap_level_before_texstorage
Result of abs(i) where i is an integer in vertex shader is wrong: 642227
Applied Workarounds: emulate_abs_int_function
Rewrite texelFetchOffset to texelFetch for Intel Mac: 642605
Applied Workarounds: rewrite_texelfetchoffset_to_texelfetch
Rewrite condition in for and while loops for Intel Mac: 644669
Applied Workarounds: add_and_true_to_loop_condition
Rewrite do-while loops to simpler constructs on Mac: 644669
Applied Workarounds: rewrite_do_while_loops
AVSampleBufferDisplayLayer leaks IOSurfaces on 10.9.: 632178
Applied Workarounds: disable_av_sample_buffer_display_layer
Do TexImage2D first before CopyTexImage2D for cube map texture on Intel Mac 10.11: 648197
Applied Workarounds: init_one_cube_map_level_before_copyteximage
Decode and encode before generateMipmap for srgb format textures on macosx: 634519
Applied Workarounds: decode_encode_srgb_for_generatemipmap
Insert statements to reference all members in unused std140/shared blocks on Mac: 618464
Applied Workarounds: use_unused_standard_shared_blocks
Tex(Sub)Image3D performs incorrectly when uploading from unpack buffer with GL_UNPACK_IMAGE_HEIGHT greater than zero on Intel Macs: 654258
Applied Workarounds: unpack_image_height_workaround_with_unpack_buffer
adjust src/dst region if blitting pixels outside read framebuffer on Mac: 644740
Applied Workarounds: adjust_src_dst_region_for_blitframebuffer
Mac driver GL 4.1 requires invariant and centroid to match between shaders: 639760, 641129
Applied Workarounds: remove_invariant_and_centroid_for_essl3
Version Information
Data exported	2/23/2017, 2:42:10 PM
Chrome version	Chrome/56.0.2924.87
Operating system	Mac OS X 10.10.5
Software rendering list version	12.06
Driver bug list version	9.24
ANGLE commit id	a4aaa2de57dc
2D graphics backend	Skia/56 bf2d9e02d58ea01f1c239f7e2fc024cba140ccb1
Command Line Args	Chrome.app/Contents/MacOS/Google Chrome --flag-switches-begin --enable-experimental-web-platform-features --flag-switches-end
Driver Information
Initialization time	0
In-process GPU	true
Sandboxed	false
GPU0	VENDOR = 0x1002, DEVICE= 0x6741
GPU1	VENDOR = 0x8086, DEVICE= 0x0126 *ACTIVE*
Optimus	false
AMD switchable	true
Driver vendor	
Driver version	
Driver date	
Pixel shader version	
Vertex shader version	
Max. MSAA samples	
Machine model name	MacBookPro
Machine model version	8.2
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	Zero-copy
Partial Raster	Enabled
GpuMemoryBuffers Status
ATC	Software only
ATCIA	Software only
DXT1	Software only
DXT5	Software only
ETC1	Software only
R_8	GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
RG_88	Software only
BGR_565	Software only
RGBA_4444	Software only
RGBX_8888	Software only
RGBA_8888	GPU_READ, SCANOUT
BGRX_8888	GPU_READ, SCANOUT
BGRA_8888	GPU_READ, SCANOUT, GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
YVU_420	Software only
YUV_420_BIPLANAR	GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
UYVY_422	GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT

Comment 4 by kbr@chromium.org, Feb 23 2017

Cc: kainino@chromium.org ccameron@chromium.org
Mergedinto: 592130
Status: Duplicate (was: Unconfirmed)
Sorry, but your Mac contains an Intel HD 3000 GPU which has been highly problematic. Chrome has disabled its use of all GPU features on any Mac containing this GPU. You can launch Chrome from the Terminal with the command line argument --ignore-gpu-blacklist but we don't support that configuration.

Is this documented anywhere other than a blink-dev or other similar group? The fact that it used to work in earlier versions of Chrome makes me wonder what the big problems are.

I don't have permission to view the bug this was merged into. Is it possible to make it public? 
Yes, as kbr said above.

The flag can be changed from within Chrome at chrome://flags/#ignore-gpu-blacklist , but if you use this, you may encounter bugs that won't ever be fixed.
The issue that this was merged into is a full system hang issue due to a bug in the GPU/driver:

> 1.  Launch Chrome on a MacBook that uses the Intel HD 4000 Graphics Card
> 2.  Leave the browser open for a few minutes, or navigate to gmail.com or play a video on youtube for a few minutes
> 3.  Computer display will go blank and need to be force rebooted or computer will completely power off

As such - the only way we know to reliably avoid crashing users' computers is to disable GPU use entirely.
I don't think this is enough. I will ask again if there is any place where this is documented outside the bug and outside the blacklist so that non-technical users can see what GPUs are disabled for different OSs.

Still don't understand why the bug is not publicly accessible but the responses tell me it will not be solved so I'll have to look for alternatives. 

Sign in to add a comment