Couldn't find any crash reports for the site in question. Could you please upload a crash dump by visting chrome://crashes/ in a separate tab after the error occurs.

Here you have the image of chrome://crashes/

Deleted: Screen Shot 2017-05-10 at 11.22.27.png 137 KB

	Screen Shot 2017-05-10 at 11.22.27.png 137 KB View Download

None of these crashes are recent, so it is not a crash. Instead, there must be some other kind of error coming out of the command buffer.

Please copy+paste your chrome://gpu contents into a comment here. It is required for all GPU-related bug reports, otherwise we cannot reproduce.

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_framebuffer_cmaa
disable_multimonitor_multisampling
disable_webgl_rgb_multisampling_usage
emulate_abs_int_function
get_frag_data_info_bug
init_two_cube_map_levels_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
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_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: flash_stage3d, gpu_compositing, panel_fitting, flash3d, gpu_rasterization, accelerated_2d_canvas, accelerated_video_decode, webgl2, accelerated_vpx_decode, accelerated_webgl, flash_stage3d_baseline, accelerated_video_encode
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
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
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
Decode and encode before generateMipmap for srgb format textures on macosx: 634519
Applied Workarounds: decode_encode_srgb_for_generatemipmap
Init first two levels before CopyTexImage2D for cube map texture on Intel Mac 10.12: 648197
Applied Workarounds: init_two_cube_map_levels_before_copyteximage
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
Disable KHR_blend_equation_advanced until cc shaders are updated: 661715
Version Information
Data exported	5/10/2017, 1:03:09 PM
Chrome version	Chrome/60.0.3088.3
Operating system	Mac OS X 10.12.4
Software rendering list version	13.4
Driver bug list version	10.5
ANGLE commit id	d262799c3784
2D graphics backend	Skia/60 ad15264f9ad2aa62e1da1ab3105887503ddeb4e9-
Command Line	/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --flag-switches-begin --enable-es3-apis --enable-webgl-draft-extensions --flag-switches-end
Driver Information
Initialization time	0
In-process GPU	true
Passthrough Command Decoder	false
Supports overlays	false
Sandboxed	false
GPU0	VENDOR = 0x1002, DEVICE= 0x6740
GPU1	VENDOR = 0x8086, DEVICE= 0x0126 *ACTIVE*
Optimus	false
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.3
GL_VENDOR	
GL_RENDERER	
GL_VERSION	
GL_EXTENSIONS	
Disabled Extensions	GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent
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, SCANOUT_CPU_READ_WRITE
BGRX_8888	GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE
BGRA_8888	GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
RGBA_F16	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

Deleted: Screen Shot 2017-05-10 at 13.05.24.png 42.1 KB

	Screen Shot 2017-05-10 at 13.05.24.png 42.1 KB View Download

Deleted: Screen Shot 2017-05-10 at 13.05.35.png 32.7 KB

	Screen Shot 2017-05-10 at 13.05.35.png 32.7 KB View Download

Thank you for providing more feedback. Adding requester "kainino@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

+ericrk

WebGL is unfortunately not supported at all on your configuration. The Intel HD 3000 on Mac has been found to be very unstable so we have disable WebGL to prevent much more serious browser crashes. I think Matterport's error message is slightly misleading - there was no crash; WebGL is simply not available.

WebGL was recently disabled on Mac with HD3000 and switchable graphics - it was meant to be disabled already in issue 592130 but it was really disabled for multi-gpu configurations in  issue 661596  (starting with Chrome 57).

One way for us to avoid this issue would be to always use the discrete GPU on multi-GPU systems that include HD 3000. @ericrk, do you have any thoughts on this approach? Power usage would be my immediate concern.

Supporting SwiftShader on Mac (see  issue 719257 ) would also provide a slower fallback to avoid this issue.

But what about Fireforx and Safari both of them works fine

Deleted: Screen Shot 2017-05-10 at 13.46.06.png 1.1 MB

	Screen Shot 2017-05-10 at 13.46.06.png 1.1 MB View Download

Deleted: Screen Shot 2017-05-10 at 13.46.31.png 1.2 MB

	Screen Shot 2017-05-10 at 13.46.31.png 1.2 MB View Download

They're either using the AMD GPU, or (more likely) they're using the Intel GPU despite its instability. Perhaps they just run into fewer bugs on Intel HD 3000 than Chrome does.

If you really want to enable Chrome to use the GPU on your machine, you can enable chrome://flags/#ignore-gpu-blacklist , but be warned that it may make Chrome less stable, and GPU may get disabled due to crashes anyway.

There is another possibility: the reason we disable GPU acceleration in that Mac is the Intel HD 3000. On that MacBook, there is another GPU (discrete GPU) that are good to run GPU acceleration.

So instead of blacklist GPU acceleration, we can force Chrome to run on discrete GPU. The downside is now the battery life will be much shorter.

Per offline discussion with ccameron, we will force to discrete GPU on the MacBook with dual GPUs and one of them is Intel HD 3000. That way, we will get GPU acceleration and WebGL back.

For Macbook with only one GPU, which is Intel HD 3000, GPU acceleration will still be off.

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

commit 0a54d442752d12ee4e341ac62c43f4fd84a64434
Author: zmo <zmo@chromium.org>
Date: Thu May 11 22:53:02 2017

Move dual GPU macbook with Intel HD 3000 out of blacklist.

Instead of disabling all GPU features because Intel HD 3000 is crash prone,
we force Chrome to use discrete GPU.

On the up side, now we can get WebGL back. On the down side, now Chrome on these
macbooks will burn energy more quickly.

BUG= 720152 
TEST=affected macbook
R=ccameron@chromium.org
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/2874163003
Cr-Commit-Position: refs/heads/master@{#471103}

[modify] https://crrev.com/0a54d442752d12ee4e341ac62c43f4fd84a64434/gpu/config/gpu_driver_bug_list.json
[modify] https://crrev.com/0a54d442752d12ee4e341ac62c43f4fd84a64434/gpu/config/software_rendering_list.json

After the above CL, MacBook with dual GPUs (one is Intel HD 3000) should get back GPU acceleration on the discrete AMD GPU.