PS: Activating hardware acceleration solves the issue, but the default setting in Chrome seems to be disabled.

On a recent model MacBook Pro, hardware acceleration should not be disabled by default.  The chrome://gpu dump you provided looks fishy.  Are you using Chrome inside a VM or through a remote desktop session, or something like that?

What das fishy mean? I have a VPN app installed on my system (No Chrome Extension), but I only run it sporadically for certain websites.

What should happen when I manually disable hardware acceleration and then reset all flags and settings? For me the hardware acceleration stays disabled every time, even after reinstalling Chrome.

MacBook Pro (13-inch, 2017)
Iris Plus Graphics 650 1536 MB

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

By "fishy", I mean suspicious.  According to your chrome://gpu page, Chrome is not recognizing your graphics hardware correctly. It is detecting the correct device ID, but the wrong features. The VPN app would not cause this.

Ligi, do we have one of these machines in house?

Sorry Ken, we don't have 2017 MBP.

PS: I do not see this issue on (13-inch, Late 2016, Intel iris Graphics 550 1536 MB) MBPro.

Unable to reproduce the issue on reported version 62.0.3202.94 and the latest build 64.0.3275.0 when hardware acceleration is in enable mode
few observations are as folows:
i) When we enable the hardware acceleration we are able to see the cube spinning 
ii) When we disable the hardware acceleration and relaunch the chrome, then we are seeing the same message as mentioned in comment#0 screenshot
Please find the attached screen cast for your reference

Note: Even after reinstalling and uinstalling the chrome we are seeing hardware acceleration is in default enable mode

Can anyone from the Internals>GPU>VendorSpecific team please have a look at this issue, as the issue is not reproducible from TE end"

Here's my GPU dump with hardware acceleration enabled. Is it still fishy?

Deleted: chrome___gpu.pdf 113 KB

chrome___gpu.pdf 113 KB Download

michelluarasi@: it seems wrong that you have to specify --ignore-gpu-blacklist in order to get GPU acceleration in Chrome. I wonder if you have antivirus software or something else installed which is interfering with Chrome's normal operation.

If you launch from the command line with:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --user-data-dir=/tmp/t1

(which will start with a fresh user-data-dir)

does the problem still happen?

Instead of a PDF, can you please just copy-paste the entire contents of about:gpu in plaintext form? We need to see if there are any logging messages at the bottom of the page.

Unless we can get one of these exact machines in house and try to reproduce, I don't think we can make progress on this bug. Mano or others, can you try to procure one?

I disabled the flag "--ignore-gpu-blacklist" and webgl works now with hardware acceleration enabled.

The reset function behaves weird from an ux perspective: If i reset the browser from the settings, i expect everything to be set to default (incl. flags). The reset modal should have more and precise options.

For me everything works now by manually enabling hardware acceleration.

Deleted: reset-chrome.mov 6.1 MB

reset-chrome.mov 6.1 MB Download

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

michelluarasi@: Thank you for providing the screen-cast

Thsese are the only changes which will be restored on clicking reset button on setting page
Default search engine, Homepage and tabs, The new tab page, Tabs that you have pinned, Content settings, Cookies and site data, Extensions and themes

Please find the attached screenshot and below link for more information and report back 
https://support.google.com/chrome/answer/3296214?visit_id=0-636471023724541126-1461239210&p=ui_reset_settings&rd=1

This sounds like a user configuration error. Please reopen if there are more widespread instances.