Chrome Version is 60.0.3112.90 (Official Build) (64-bit)

leo.ingson@ Thank you for the issue.

Unable to reproduce the issue on Windows 7 and Mac OS 10.12.6 using latest Stable 60.0.3112.90 and canary 62.0.3182.0 with the below steps

1. Launched Chrome and browsed news, images, videos. 
2. No issues were observed,

Please find the attached screen cast and confirm if anything is missed here.
Request you please retry the issue on new profile and provide us the screen cast for better understanding of the issue. 
Please update the thread if the issue still exists.

Thanks..

Deleted: 754208.webm 16.2 MB

754208.webm 16.2 MB Download

Sorry for the delay, emails got spam tagged.
More info: The GPU flicker also happens with an empty tab (no URL).

Here are some screenshots:
1. Launched chrome, open new tab - patterns, some flicker.
2. Launched chrome, open "about chrome" - patterns, some flicker.
3. Launched chrome using open Terminal /Applications/Google\ Chrome.app --args --disable-gpu , open anything - works

Deleted: chrome gpu 1__empty page.png 387 KB

	chrome gpu 1__empty page.png 387 KB View Download

Deleted: chrome gpu 2__about chrome.png 356 KB

	chrome gpu 2__about chrome.png 356 KB View Download

Deleted: chrome gpu 3__about chrome__--disable-gpu.png 156 KB

	chrome gpu 3__about chrome__--disable-gpu.png 156 KB View Download

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

You can see OSX version + GPU in use in screenshot 1 lower right corner.
Correct Terminal launch command for disabled GPU is (typo):
open /Applications/Google\ Chrome.app --args --disable-gpu

New tabs are not really empty - they show google and last open tabs. So no wonder that GPU flicker happens..

Just learned screencasting and re-encoding on a Mac:
1. chrome with GPU
2. chrome without GPU

Deleted: chrome_w_gpu.webm 7.7 MB

	chrome_w_gpu.webm 7.7 MB View Download

Deleted: chrome_w_o_gpu.webm 2.7 MB

	chrome_w_o_gpu.webm 2.7 MB View Download

Tested the issue using latest stable #60.0.3112.101 on Win 10, and was unable to reproduce the issue. No such broken behavior is seen.

Requesting Internals>GPU team for further action on this issue.

Thanks!!

60.0.3112.101 (Official Build) (64-bit) on OSX 10.10.5: same behaviour (see GPU specs above).

Could you please try flag --disable-gpu-rasterization instead of --disable-gpu?  If that works, please attach a copy of output from "chrome://gpu".

sandeepkumars@ this has to be OS version and GPU specific.  Do we have any way to test a similar MBP with OS X 10.10.5?

From screenshot #1 in comment #4, this seems to be a Late 2011 MBP with Intel HD3000 + Radeon 6750M graphics. We'll need the output of chrome://gpu to know which GPU was active.

Looking at the MBP model (Late 2011 with HD3000/Radeon 6750) GPU raster should be disabled. It's blacklisted for both Intel (vendor 0x8086, device ID 0x0116 or 0x0126) and AMD (vendor 0x1002, device ID 0x6741). The pattern of corruption seems to show square tiles, which reinforces SW raster.

1/ --disable-gpu-rasterization does not work, square tiles as in screenshots above
2/ Late 2011 MBP with Intel HD3000 + Radeon 6750M graphics is correct. AFAIK it's always external GPU working (Radeon) when "Automatic graphics switching" is enabled in "energy Saver" settings of OSX. I don't know how to detect which one is working. Forcing to internal Intel Graphics seems rather complex (EFI..).
3/ other GPU stuff seems to work just fine: google earth, firefox/safari/vivaldi
  - GPU of late 2011 MacbookPro sometimes has heat problems (soldering) - mainboard exchanged, seems to work now
3/ chrome://gpu output anyways (--disable-gpu, else not readable):
Graphics Feature Status
Canvas: Software only. Hardware acceleration disabled
CheckerImaging: Disabled
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 disabled
Video Encode: Software only, hardware acceleration unavailable
WebGL: Unavailable
WebGL2: Unavailable
Driver Bug Workarounds
adjust_src_dst_region_for_blitframebuffer
decode_encode_srgb_for_generatemipmap
disable_av_sample_buffer_display_layer
disable_framebuffer_cmaa
disable_multimonitor_multisampling
disable_multisampling_color_mask_usage
get_frag_data_info_bug
pack_parameters_workaround_with_pack_buffer
regenerate_struct_names
remove_invariant_and_centroid_for_essl3
reset_base_mipmap_level_before_texstorage
rewrite_do_while_loops
scalarize_vec_and_mat_constructor_args
set_zero_level_before_generating_mipmap
unfold_short_circuit_as_ternary_operation
unpack_alignment_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: GPU access is disabled through commandline switch --disable-gpu.
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
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
glColorMask does not work for multisample renderbuffers on old AMD GPUs.: 595948
Applied Workarounds: disable_multisampling_color_mask_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
glTexStorage* are buggy when base mipmap level is not 0: 640506
Applied Workarounds: reset_base_mipmap_level_before_texstorage
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
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
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
Accelerated 2D canvas is unavailable: either disabled via blacklist or the command line.
Disabled Features: 2d_canvas
Accelerated video decode has been disabled, either via blacklist, about:flags or the command line.
Disabled Features: video_decode
Checker-imaging has been disabled via finch trial or the command line.
Disabled Features: checker_imaging
Version Information
Data exported	8/24/2017, 10:48:40 PM
Chrome version	Chrome/60.0.3112.101
Operating system	Mac OS X 10.10.5
Software rendering list version	13.8
Driver bug list version	10.93
ANGLE commit id	3e6a61fecba9
2D graphics backend	Skia/60 d1f2d15b36f6a6a9d199581b998a7ca924a1f1a8-
Command Line	/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --disable-gpu --flag-switches-begin --disable-accelerated-2d-canvas --disable-accelerated-video-decode --enable-es3-apis --disable-gpu-rasterization --disable-zero-copy --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= 0x6741 *ACTIVE*
GPU1	VENDOR = 0x8086, DEVICE= 0x0116
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.2
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	One-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

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

Used graphics card is shown in "activity monitor" tab "energy". When nothing happens, "integrated card" is used. Whenever I start chrome, it goes to "High Perf." after 2secs, before any rendering can happen (tried chrome://gpu). Thus all the above findings are Radeon GPU rendering.

1/ chrome obviously switches on the Radeon - never goes away when chrome runs.
2/ Radeon details:
AMD Radeon HD 6750M:

  Chipset Model:	AMD Radeon HD 6750M
  Type:	GPU
  Bus:	PCIe
  PCIe Lane Width:	x8
  VRAM (Total):	512 MB
  Vendor:	ATI (0x1002)
  Device ID:	0x6741
  Revision ID:	0x0000
  ROM Revision:	113-C0170L-573
  gMux Version:	1.9.23
  EFI Driver Version:	01.00.573

Any use of chrome://flags/  ??

HD3000 was super-buggy and we blacklisted all GPU acceleration in https://codereview.chromium.org/2076443002/. Perhaps we should extend this to all dual GPU systems with an HD3000?

Can you try with the argument --disable-mac-overlays? We could also consider disabling Mac overlays for older configurations (it comes with a battery hit).

It sounds like we should blacklist on a system with HD3000 in any slot.

--disable-mac-overlays does not work, square tiles as in screenshots above

 Issue 750966  has been merged into this issue.

Rendering is ok with internal Intel HD3000 GPU via --force_discrete_gpu=0

PS: Having to solve 5 captchas for an entry sucks

Rendering with --force_discrete_gpu=0 not working anymore - maybe related to new Version 60.0.3112.113 (Official Build) (64-bit)

I don't understand why --force_discrete_gpu=0 would make a difference because looking at the about:gpu content you provided, force_discrete_gpu isn't on.

If you want to force it on integrated gpu, please use --force_integrated_gpu=1 instead.

Updating from OSX Yosemite (10.10.5) to Sierra (10.12.6, plus security updates) seemed to have helped - no more GPU flicker, as I realized by accidentally starting chrome w/o --disable-gpu

I guess something was wrong with the requirements for 60.0.3112.90 (Official Build) (64-bit)..

Too early - no more flicker, but of all pages google.de sometimes does not render (search started using the url line).
62.0.3202.94 (Official Build) (64-bit)

Can be closed

Problem seems gone at 63.0.3239.108 (Official Build) (64-bit)  (or a little earlier).

leo.ingson@, thank you for the update! Please feel free to file a new bug for any further issues with chrome in future.