This is for Windows 7 SP1 64 Bit OS.

Hi Anthony,

Please try running the browser with the '--disable-gpu' flag. This is achieved by following the steps below:

1.) Right click the Chrome shortcut.
2.) Click on Properties.
3.) Look for the 'target' field, and at the very end of the string type a space, and then '--disable-gpu' (without the quotas.)

Make sure to close all Chrome.exe processes in the task manager and then open Chrome using the shortcut you just modified. If this works, check if there are updates available for your Graphic card drivers, and try to find out whether all the affected machines have the same exact graphic card so you can narrow the issue down.

Additionally, please check if the issue is reproducible in current Beta release. You can get it from  https://www.google.com/chrome/browser/beta.html. Please note that Beta is installed on top of the current Stable installation and should be used for testing purposes only. If issue is not present in Beta, chances are that the next Stable release will fix the problem for you.

Thanks!

To address your questions to the email (I do not have option to email directly).

1.) Yes, the policy to disable hardware acceleration should do the same.
2.) There's a flag to make Chrome capture logs, and that is '--enable-logging --v=1'. More details at https://www.chromium.org/for-testers/enable-logging. However I'm not sure if this will capture valuable information for GPU-related problems.
3.) Beta will be installed on top of the current installation, no need to uninstall the stable one. Please do it in a couple of tests affected computers only.
4.) Chrome MSI should not re-install on top of the current installation unless the current installation is older. I've not tested this recently, but it used to be this way.

Additionally, in your email you mentioned that you used '-disable-gpu', not sure if it's a typo in the email, or you actually used the flag with just one dash symbol. Note that for the flag to work, you have to put double dash at the beginning. To look current flags that the browser is running with, please navigate to chrome://version, you'll see all flags that have been manually added in between --flag-switches-begin and --flag-switches-end. If a flag you've put into the shortcut is not listed there, it means that it was not set up correctly due to either a typo, or the flag is not available to be used anymore. You may also try with '--disable-extensions', and '--disable-plugins'.

As a side note, I've seen some similar issues if there's more than 1 monitor, if that's case, you can try leaving the computer with just one monitor and see the outcome.

Hi Anthony,

I think that Windows by itself will not install any MSI if there's a new version of the software installed. I can try this out, but maybe next week, I'll have to set up a virtual server/client.

Version 60 stable should be around the corner, tentatively on July 26th. You can check the releases calendar at https://www.chromium.org/developers/calendar.

Looks like this is being followed up by hernandezma@ through email. Cc'ing for further action on this.

anthony.arebalo@: Could you please confirm if this is reproducible on the latest stable(60.0.3112.90) as well?

Hello,

It seems like the version we are laying down (57.2987.133), no matter what version it is upgraded to, the crash happens.  I will build a new package with the latest version to see if this solves the issue. 

Thanks

Re-tried the issue again on Windows 7, Mac OS 10.12.6 on the latest Stable 61.0.3163.100 and Canary 63.0.3237.7 and unable to reproduce the issue.
Closing this issue as there is no update from the reporter for more than a month as per comment #7.

Please feel free to file a new issue if there are any issues on the latest chrome versions.

Thanks..