This seems a lot like  issue 794541 . This is the second report that I've seen today about this.

Anyone owning these graphics corruption issues?

There's chatter and screenshots of the issues on Twitter — seems to be affecting several folks.

Deleted: Screen Shot 2017-12-13 at 10.41.55 PM.png 582 KB

	Screen Shot 2017-12-13 at 10.41.55 PM.png 582 KB View Download

Deleted: Screen Shot 2017-12-13 at 10.42.04 PM.png 770 KB

	Screen Shot 2017-12-13 at 10.42.04 PM.png 770 KB View Download

Deleted: Screen Shot 2017-12-13 at 10.42.15 PM.png 847 KB

	Screen Shot 2017-12-13 at 10.42.15 PM.png 847 KB View Download

Deleted: Screen Shot 2017-12-13 at 10.42.27 PM.png 439 KB

	Screen Shot 2017-12-13 at 10.42.27 PM.png 439 KB View Download

Deleted: Screen Shot 2017-12-13 at 10.42.45 PM.png 304 KB

	Screen Shot 2017-12-13 at 10.42.45 PM.png 304 KB View Download

 Issue 794912  has been merged into this issue.

Unable to reproduce this issue on reported version 62.0.3202.94, on latest stable 63.0.3239.108 and on latest canary 65.0.3294.3 using Mac 10.13.1 and Mac 10.12.6 with steps mentioned below.

Navigated to sites like Amazon.com,facebook.com and wikipedia.coma nd observed page loaded successfully and content is seen without any issue.

@Reporter: Please provide contents of chrome://gpu. This would help in further triaging of the issue.

Thanks!

 Issue 795162  has been merged into this issue.

Unfortunately the chrome://gpu is not legible (screenshot is attached).

I am not having these problems in Chrome stable, only Canary. 

Deleted: Screen Shot 2017-12-15 at 12.08.05.png 399 KB

	Screen Shot 2017-12-15 at 12.08.05.png 399 KB View Download

I am seeing the same issue on Canary version for Mac. I am unable to see anything due to the broken glass problem so not sure which version it is affecting exactly. Posting this through the stable version.

I restarted everything, deleted all profiles but see the same issue.

From a small sample, the problem seems to affect Intel integrated GPUs in particular as it doesn't seem to manifest when using ATI or Nvidia GPUs.

 Issue 795522  has been merged into this issue.

 Issue 795466  has been merged into this issue.

Plenty of reports for this now from Chrome discussion forum for Mac Canary Chrome:

https://productforums.google.com/forum/#!topicsearchin/chrome/category$3Amac$20canary$20display%7Csort:date

I have the same problem too

I have had the same problem with the latest Canary build.  This does NOT occur with the latest Chrome Stable.  I have tested Canary as a clean install after removing all remnants of Canary and then reinstalling from the latest Canary download and it does not resolve the issue.

My system is a Mac Book Air with "Intel HD Graphics 5000 1536 MB" video.  I'm currently running Mac OS 10.11.6.

All web content in all tabs is affected by this video issue including any website loaded or even "chrome://settings/", "chrome://settings/help", "chrome://extensions/", Developer Tools, etc. 

Also seeing on Chrome Canary on 15in 2015 MBP, OSX 10.11.6

I'm getting this issue on the latest stable build on my Mac. It isn't exclusive to just Chrome canary.

 Issue 795630  has been merged into this issue.

Everyone who is affected by this, please go to about:gpu, print the page as a PDF, and attach it.

 Issue 794541  has been merged into this issue.

Has anyone at google been able to reproduce this issue?

Anantha, has anyone been able to reproduce this issue locally?

For the people affected, could you let me know if running from the command line with the following flags do anything (just use them one at a time)?

  --disable-mac-overlays
  --disable-remote-core-animation
  --disable-gpu-rasterization

Thanks!

It was tough but was able to save the PDF for about:gpu, attached it here

Deleted: gpu.pdf 121 KB

gpu.pdf 121 KB Download

Sounds like this might be 10.11 only, and a fairly deep graphics driver bug.

Not easy to do, but was successful after sometime. GPU PDF attached.

Deleted: Chrome GPU.pdf 109 KB

Chrome GPU.pdf 109 KB Download

There's a possibility that this is related to the fix for  Issue 786358 , which affected the pixel storage parameters on the service side.

I tried the flags you mentioned above. Chrome renders everything correctly when I use the --disable-gpu-rasterization flag from command line

This looks to be specific to macOS 10.10 and 10.11, and Intel GPUs.

about:gpu attached with "--disable-gpu-rasterization", which did resolve the display issues.

Chrome Canary on 15in 2015 MBP, OSX 10.11.6

Deleted: gpu.pdf 124 KB

gpu.pdf 124 KB Download

While most of the sites work fine, I did see the same issue when I opened Google Docs even after using the --disable-gpu-rasterization flag

Doesn't reproduce on an Intel HD 6000 with 10.11.6. about:gpu follows. Will test on an Intel HD 5000 next.

Ran a couple of image searches, Google Docs. A couple of errors were generated regarding unsupported texture formats, which are a bit worrisome.

Graphics Feature Status
Canvas: Hardware accelerated
CheckerImaging: Disabled
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Hardware accelerated
Rasterization: Hardware accelerated
Video Decode: Hardware accelerated
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
Driver Bug Workarounds
add_and_true_to_loop_condition
adjust_src_dst_region_for_blitframebuffer
avoid_stencil_buffers
clear_to_zero_or_one_broken
decode_encode_srgb_for_generatemipmap
disable_framebuffer_cmaa
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_float_unary_minus_operator
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
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
Use GL_INTEL_framebuffer_CMAA on ChromeOS: 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
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
Disable KHR_blend_equation_advanced until cc shaders are updated: 661715
Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent)
Rewrite -float to 0.0 - float for Intel Mac: 672380
Applied Workarounds: rewrite_float_unary_minus_operator
Certain Apple devices leak stencil buffers: 713854
Applied Workarounds: avoid_stencil_buffers
glClearColor does not always work on Intel 6xxx Mac drivers: 710443
Applied Workarounds: clear_to_zero_or_one_broken
Checker-imaging has been disabled via finch trial or the command line.
Disabled Features: checker_imaging
Version Information
Data exported	12/18/2017, 2:35:24 PM
Chrome version	Chrome/65.0.3298.0
Operating system	Mac OS X 10.11.6
Software rendering list URL	https://chromium.googlesource.com/chromium/src/+/6586a208880a70a00856529493741971ecfea5c2/gpu/config/software_rendering_list.json
Driver bug list URL	https://chromium.googlesource.com/chromium/src/+/6586a208880a70a00856529493741971ecfea5c2/gpu/config/gpu_driver_bug_list.json
ANGLE commit id	647dca7672f7
2D graphics backend	Skia/65 ef0384835757df463f5157145650a60ba8b14a63-
Command Line	/Applications/Google Chrome Canary.app/Contents/MacOS/Google Chrome Canary -psn_0_266305 --flag-switches-begin --flag-switches-end
Driver Information
Initialization time	75
In-process GPU	false
Passthrough Command Decoder	false
Direct Composition	false
Supports overlays	false
Sandboxed	true
GPU0	VENDOR = 0x8086, DEVICE= 0x1626 *ACTIVE*
Optimus	false
Optimus	false
AMD switchable	false
Driver vendor	
Driver version	10.14.73
Driver date	
Pixel shader version	4.10
Vertex shader version	4.10
Max. MSAA samples	8
Machine model name	MacBookAir
Machine model version	7.2
GL_VENDOR	Intel Inc.
GL_RENDERER	Intel(R) HD Graphics 6000
GL_VERSION	4.1 INTEL-10.14.73
GL_EXTENSIONS	GL_ARB_blend_func_extended GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_ES2_compatibility GL_ARB_explicit_attrib_location GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader5 GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_occlusion_query2 GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_subroutine GL_ARB_shading_language_include GL_ARB_tessellation_shader GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_cube_map_array GL_ARB_texture_gather GL_ARB_texture_query_lod GL_ARB_texture_rgb10_a2ui GL_ARB_texture_storage GL_ARB_texture_swizzle GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_vertex_attrib_64bit GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_texture_compression_s3tc GL_EXT_texture_filter_anisotropic GL_EXT_texture_sRGB_decode GL_APPLE_client_storage GL_APPLE_container_object_shareable GL_APPLE_flush_render GL_APPLE_object_purgeable GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_texture_range GL_ATI_texture_mirror_once GL_NV_texture_barrier
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, SCANOUT, GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
R_16	Software only
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
BGRX_1010102	Software only
BGRA_8888	GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
RGBA_F16	GPU_READ, SCANOUT, GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
YVU_420	Software only
YUV_420_BIPLANAR	GPU_READ, SCANOUT, GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
UYVY_422	GPU_READ, SCANOUT, GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
Display(s) Information
Info	Display[69679040] bounds=0,0 1440x900, workarea=0,23 1440x800, scale=1, external
Color space information	{primaries:[[0.3806,0.4340,0.1496,],[0.2195,0.6820,0.0985,],[0.0401,0.0883,0.6966,],], transfer:0.0774*x + 0.0000 if x < 0.0404 else (0.9479*x + 0.0521)**2.4000 + 0.0000, matrix:RGB, range:FULL}
Bits per color component	8
Bits per pixel	24
Video Acceleration Information
Decode h264 baseline	up to 4096x2160 pixels
Decode h264 extended	up to 4096x2160 pixels
Decode h264 main	up to 4096x2160 pixels
Decode h264 high	up to 4096x2160 pixels
Encode h264 baseline	up to 4096x2160 pixels and/or 30.000 fps
Encode h264 main	up to 4096x2160 pixels and/or 30.000 fps
Encode h264 high	up to 4096x2160 pixels and/or 30.000 fps
Log Messages
[774:775:1218/143523.347938:ERROR:gles2_cmd_decoder.cc(18206)] : [.DisplayCompositor-0x7fe0ba16ea00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[774:775:1218/143523.348035:ERROR:gles2_cmd_decoder.cc(12406)] : [.DisplayCompositor-0x7fe0ba16ea00]GL ERROR :GL_INVALID_VALUE : glScheduleCALayerCHROMIUM: unsupported texture format
[774:775:1218/143523.348090:ERROR:gles2_cmd_decoder.cc(18206)] : [.DisplayCompositor-0x7fe0ba16ea00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[774:775:1218/143523.348172:ERROR:gles2_cmd_decoder.cc(12406)] : [.DisplayCompositor-0x7fe0ba16ea00]GL ERROR :GL_INVALID_VALUE : glScheduleCALayerCHROMIUM: unsupported texture format

Reproducible on Intel HD 5000. Bisecting.

The problem was introduced in this Skia roll:


You are probably looking for a change made after 523503 (known good), but no later than 523504 (first known bad).
CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.
  https://chromium.googlesource.com/chromium/src/+log/5126c5ebd3e5a72b9e136e6ef6eef5685458c449..f31bb407c71e169baa5ef9cd451d1534c8dc4a4f

My best guess is probably https://skia.googlesource.com/skia.git/+/e7e81c15c144b8133f696d0744ed9f7e8d06e936 .

Is anyone from the Skia team available to help bisect into that roll?

Note to anyone affected by this bug: upgrading to either 10.12 or 10.13 will work around it -- confirmed on our Intel HD 5000 machine.

CC'ing Yunchao from Intel as an FYI that there's a pretty bad bug in older macOS graphics drivers for some GPUs.

I think Chrome should probably just disable GPU rasterization on Intel GPUs on these older OS releases as a mitigation.

Thanks for the info, Ken. 
@bsalomon and @fmalita, could Skia team bisect into the skia roll Ken pointed out at the same time？

Unfortunately I don't have access to an HD 5000 machine to bisect.  I recall there was one in the office at some point though, so maybe bsalomon@ can help.

Is upgrading MacOS to 10.12 or 13 the only solution to this problem?

same problem here
Model Name:	MacBook Pro
  Model Identifier:	MacBookPro11,4
  Processor Name:	Intel Core i7


AMC OS 10.11.6 (15G18013)

Here's another about:gpu only made possible with --disable-gpu-rasterization, but the tearing still occurs in Google Sheets. Other sites seem to work fine so far.

Deleted: gpu.pdf 123 KB

gpu.pdf 123 KB Download

The last time we had an Intel Haswell graphics issue I borrowed a colleague's  corp laptop. It was already running 10.13.

Re #36, I agree on blacklisting.

From #41 it seems disabling GPU rasterization doesn't resolve the issue.

@zmo do you mean #42?

Google Sheets likely uses Canvas2d, which doesn't observe --disable-gpu-rasterization (attached gpu info shows Canvas: Hardware accelerated).

@adrien.monteleone could you verify that --disable-accelerated-2d-canvas fixes Google Sheets also?

Sorry about the typo. Yes, I meant #42.

I think we should blacklist all GPU features in this case, which is unfortunate.

I can confirm that disable 2d canvas fixes the Google Sheets issue

@fmalita

I can confirm that indeed that the combination of --disable-gpu-rasterization --disable-accelerated-2d-canvas fixes Google Sheets. (disabling the canvas by itself does not)

Here's the syntax for those having trouble opening from the command line:

/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --disable-gpu-rasterization --disable-accelerated-2d-canvas 

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

commit 0f82ef114f134c9861fe37a2892e6ee9b991f634
Author: Kenneth Russell <kbr@chromium.org>
Date: Wed Dec 20 04:59:09 2017

Blacklist accelerated 2D canvas and GPU raster on old macOS/Intel.

Older macOS releases have a graphics driver bug for some Intel GPUs
triggered by recent changes in Skia.

BUG= 794819 
TBR=ericrk@chromium.org, 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
Change-Id: I0366af07c915c6fa3faa062b84dc8638b1f5dae4
Reviewed-on: https://chromium-review.googlesource.com/835791
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#525266}
[modify] https://crrev.com/0f82ef114f134c9861fe37a2892e6ee9b991f634/gpu/config/software_rendering_list.json

 Issue 795793  has been merged into this issue.

 Issue 796585  has been merged into this issue.

I tried Chrome Canary on two different Macbooks with the latest Canary 65.0.3299.0

No issues on the older 2009 Macbook Pro, i7, running OS Sierra 10.12.6
Intel HD Graphics (0x8086)
NVIDIA FeForce GT 330M

Tearing/Distortions as attached on a mid 2015 MacBook Pro i7, running Yosemite 10.10.5
Intel Iris Pro 1536 MB (0x8086)
AMD Radeon R9 M370X

Deleted: Screen Shot 2017-12-20 at 15.33.00.png 491 KB

	Screen Shot 2017-12-20 at 15.33.00.png 491 KB View Download

Canary 65.0.3299.0 was built at commit position 524906 and does not yet contain https://chromium-review.googlesource.com/835791, which landed at commit position 525266. Hopefully tomorrow's canary will contain the fix. We'd appreciate any feedback indicating whether it addresses the problem.

 Issue 796440  has been merged into this issue.

Canary 65.0.3300.0 does not resolve this issue, 
reported by me (then merged here) from https://bugs.chromium.org/p/chromium/issues/detail?id=795793

Please also note that when executing the followingcommand to disable the gpu features (temporary workaround to prevent the distortion), the following output appears.

$ /Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --disable-gpu-rasterization --disable-accelerated-2d-canvas
[55093:49411:1221/085909.821982:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &)
[55093:49411:1221/085909.854027:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &)
[55093:49411:1221/085912.134076:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &)

65.0.3300.0 is working with no noted issues when tested on the older

mid 2015 MacBook Pro i7, running Yosemite 10.10.5
Intel Iris Pro 1536 MB (0x8086)
AMD Radeon R9 M370X

I can confirm 65.0.3300.0 is working just fine for me now on:

Mac mini (Late 2014)
2.8 GHz Intel Core i5
Intel Iris 1536 MB
running El Capitan 10.11.6

same here, everything is fine now :) (65.0.3300.0) 

I'm operational again as well.

Thanks everyone for testing.

#56 (dividinglimits@), or anyone else who still sees this: please include the plaintext contents of about:gpu when reporting further occurrences. Cmd-A Cmd-C to copy it all to the clipboard, then Cmd-V in a comment to this bug report.

If you file a new bug then feel free to email me the new bug ID directly so it is triaged quickly.

Closing this as Verified. There are enough users verifying the fix that we're confident that the change we intended to make addressed the issue. The workaround might still need to be applied to other GPUs or OS versions.

Just verified that the rasterization is still reported as indicated within comment #56 and the following setup.

Chrome Canary 65.0.3300.0 (Official Build) canary (64-bit)
OSX El Capitan 10.11.6
CPU 2.2 Ghz Intel Core i7
Graphics Intel Iris Pro 1536 MB

Deleted: gpu.txt 9.5 KB

gpu.txt 9.5 KB View Download

dividinglimits@: your about:gpu says that both accelerated 2D canvas and GPU rasterization are disabled on your setup, as expected.

-----
Canvas: Software only. Hardware acceleration disabled
Rasterization: Software only. Hardware acceleration disabled

Problems Detected
Rendering artifacts on older macOS releases and Intel GPUs: 794819
Disabled Features: accelerated_2d_canvas, gpu_rasterization

Accelerated 2D canvas is unavailable: either disabled via blacklist or the command line.
Disabled Features: 2d_canvas
Accelerated rasterization has been disabled, either via blacklist, about:flags or the command line.
Disabled Features: rasterization
-----

I'm not sure why only your machine would still be affected while others with similar hardware report this fixed.

 Issue 794521  has been merged into this issue.

Started experiencing the same since yesterday on Chrome. In the middle of a project, upgrading the OS is not an option currently. Any other way to run chrome. Thanks.

Deleted: About Chrome 386 bytes

About Chrome 386 bytes View Download

Deleted: chrome-gpu-info 9.5 KB

chrome-gpu-info 9.5 KB View Download

Deleted: Screen Shot 2018-03-13 at 3.44.25 PM.png 48.7 KB

	Screen Shot 2018-03-13 at 3.44.25 PM.png 48.7 KB View Download

Deleted: Screen Shot 2018-03-13 at 3.46.24 PM.png 450 KB

	Screen Shot 2018-03-13 at 3.46.24 PM.png 450 KB View Download

And yes it does work with flags disabled
 --disable-gpu-rasterization --disable-accelerated-2d-canvas 

#92, #93: please just run Chrome with those flags. I can't explain why this workaround is working on most other peoples' machines but not on yours. The code in your browser definitely includes this workaround:

https://chromium.googlesource.com/chromium/src/+/f926414266f7aecb5ec1bf1b5f93f8716976ceef/gpu/config/software_rendering_list.json#1548

same with #92
when GPU acceleration is turned off, same thing showed up

 65.0.3325.162 Stable
OSX 10.11.6
Macbook pro retina 15-inch 2015

Started experiencing this same issue on 3/17/18. [Mac] Canary Chrome 65 - Display appears broken/tearing/shearing like shattered glass, pixelated.

OS X Yosemite Version 10.10.5
Macbook Pro Retina 13 inch, mid 2014
Chrome Version 65.0.3325.162 (Official Build) (64-bit)

Running chrome with gpu rasterization and accelerated 2d canvas flags has fixed issue (as of now).

Same issue here, the latest version of chrome is unusable on OS X.

osx version 10.11.6
MacBook Pro (Retina, 15-inch, Mid 2014)
Chrome Version 65.0.3325.181 (Official Build) (64-bit)

If you continue to experience this problem please comment on  Issue 825720  and provide the contents of about:gpu there.

#92, #93, you have --ignore-gpu-blacklist in your flags which is overriding the workaround kbr@ mentioned.