pdknsk@ thanks for the issue.

Unable to reproduce the issue on windows 7, Linux Ubuntu 14.04 and Mac 10.11.3 using chrome version 49.0.2623.110.Observed that the Rasterization: Hardware accelerated.

Please find the attached screen shot for the same.

Please try the issue once on new profile without any extensions,flags and update the thread if the issue still persists.

Thanks,

Deleted: 600499.png 434 KB

	600499.png 434 KB View Download

You have different hardware, that's why it doesn't reproduce.

Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot

Could you please provide us your chrome://gpu and OS details to triage the issue further.

Thanks,

Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Rasterization: Software only. Hardware acceleration disabled
Video Decode: Software only, hardware acceleration unavailable
Video Encode: Hardware accelerated
WebGL: Hardware accelerated

Driver Bug Workarounds
clear_uniforms_before_first_program_use
count_all_in_varyings_packing
disable_msaa_on_non_webgl_contexts
disable_post_sub_buffers_for_onscreen_surfaces
scalarize_vec_and_mat_constructor_args

Problems Detected
Accelerated 2d canvas is unstable in Linux at the moment
Disabled Features: accelerated_2d_canvas
Accelerated video decode is unavailable on Linux: 137247
Disabled Features: accelerated_video_decode
EXT_occlusion_query appears to be buggy with Intel GPUs on Linux
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Mesa drivers in Linux handle varyings without static use incorrectly: 333885
Applied Workarounds: count_all_in_varyings_packing
Disable partial swaps on linux drivers: 339493
Applied Workarounds: disable_post_sub_buffers_for_onscreen_surfaces
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
Applied Workarounds: disable_msaa_on_non_webgl_contexts
Timer queries crash on Intel GPUs on Linux: 540543, 576991
Accelerated rasterization has been disabled, either via about:flags or command line.
Disabled Features: rasterization

Driver Information
Initialization time	59
In-process GPU	false
Sandboxed	true
GPU0	VENDOR = 0x8086, DEVICE= 0x0a16
Optimus	false
AMD switchable	false
Driver vendor	Mesa
Driver version	11.0.2
Driver date	
Pixel shader version	1.30
Vertex shader version	1.30
Max. MSAA samples	8
Machine model name	
Machine model version	
GL_VENDOR	Intel Open Source Technology Center
GL_RENDERER	Mesa DRI Intel(R) Haswell Mobile
GL_VERSION	3.0 Mesa 11.0.2

Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot

Can you show your chrome://version/ contents also?

> On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
> Accelerated rasterization has been disabled, either via about:flags or command line.
> Disabled Features: rasterization

Would blacklist cause about:gpu to report the command line disabled it?

The blacklist would report that line ("Accelerated rasterization has been disabled, either via about:flags or command line."), but the reason "On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565" indicates it's a blacklist entry that disabled it.

Is this worth improving?

Sorry for the confusion. Yes, we should probably say "via blacklist entry, about:flags entry or command line."

Assigning to 'danakj@' for further action.

Thank you!

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

commit e7b47c93b032d2f1be1001bf22f2ccaaf064db95
Author: danakj <danakj@chromium.org>
Date: Fri Apr 22 23:17:32 2016

Mention blacklist when gpu compositing or raster is disabled.

R=kbr@chromium.org
BUG= 600499 

Review URL: https://codereview.chromium.org/1899693004

Cr-Commit-Position: refs/heads/master@{#389293}

[modify] https://crrev.com/e7b47c93b032d2f1be1001bf22f2ccaaf064db95/content/browser/gpu/compositor_util.cc

Thank you for the quick update on fix.