comment from user: "So just wanted to give an update. Our IT Security department uninstalled the McAfee DLP software from a test machine and are saying that Chrome then starts to function normally with the software uninstalled. I am awaiting more details, but it is looking like McAfee DLP software is to blame for the issue."

Latest comment from users:
* McAfee DLP was the issue, we were able to resolve it by pushing a different DLP Policy

* McAfee has taken this as an issue to be investigated. We are awaiting an update. The team working this  is pretty sure it is a conflict with DLP.

I tried with the Client Server test environment, chrome gets updated to latest version-58.0.3029.81. My VMs do not have McAfee installed.Seems like this is caused by McAfee Policy.

We are keeping an eye on user feedback and will report back with crash IDs if we continue to see a trend

 Issue 713023  has been merged into this issue.

In 713023, a user reports that there are lingering chrome.exe processes (browser and crashpad handler), and that killing these allows Chrome to start. Could the browser be blocked on the crashpad handler somehow?

Another user on the forums has confirmed that disabling McAfee solved the issue. danilo SARRUBBO said: "after disable McAfee it works for me"

Also got one more report from the forums: https://productforums.google.com/forum/#!topic/chrome/iKTlzPUFFf8

Making this public again to serve as a reference point for enterprises. 

+Matt for browser

Marking as fixed as this is a McAfee issue resolved by  changing DLP policy configuration. This is not something that requires changes on the Chrome side.

Latest info will be tracked here: https://productforums.google.com/forum/#!topic/chrome-admins/5Tw_-fmT_QI;context-place=forum/chrome-admins

Thanks for closing the loop. I'll follow up with the threads on the general Chrome forum links from c#1 and direct them to the admin forum thread for more info.

 Issue 714630  has been merged into this issue.

 Issue 718464  has been merged into this issue.

My enterprise does not use McAfee's DLP but we do use Solidcore and that was the culprit for us.  Disable Solidcore and it worked normally.

We are running version 6.2 of Solidcore and also have this issue. To be specific, it's the memory protection of Solidcore that is causing the Aw Snap errors. Specifically, the intersection of Chrome's 64-bit Sandboxing and Solidcore's mp-vasr-forced-relocation memory protection. Disabling that one memory protection feature resolves the issue. Also, an upgrade to version 8 of Solidcore resolved it as well.

 Issue 719354  has been merged into this issue.

 Issue 718342  has been merged into this issue.

 Issue 721799  has been merged into this issue.