Google Acknowledges Aw, Snap! Crashes in Chrome 78, you can try these workarounds

If you’ve updated Google Chrome to version 78 and noticing “Aw, Snap!” errors in Chrome when you launch it, you’re not alone, Google has acknowledged they’re aware of this issue and suggests to update Symantec Endpoint Protection to version 14.2 or later.

If you’re using Windows Defender or other third-party Antivirus such as Avast or Kaspersky other than Symantec and affected, then try this workaround as the issue is caused by Renderer Code Integrity Protection that was enabled by Chrome 78 on all Windows 10 versions.

What happened?

Google has released Chrome 78 for Windows, Mac, and Linux platforms on October 22, 2019. The new version has brought several new features and improvements.

Google has enabled Chrome to Render Integrity feature by default on Windows 10 from version 1511 or later, from version 78 onwards to “prevent unsigned modules from loading in Chrome browser’s renderer processes”.

The new feature seems to have caused Chrome users running incompatible software to receive “Aw, Snap!” errors, the reports were admitted by the Chrome team and asked users to share information in the help forum if they’re affected.

The new Chrome security feature may trigger some incompatibility issues with third-party security solutions, especially Symantec Endpoint Protection (14.0.3929.1200 and earlier), you should be updating it to 14.2 or later to avoid issues.

The workaround involves disabling Renderer Code Integrity in Chrome, here is how you can do that.

1. Right-click on Chrome shortcut on the desktop and select “Properties”

2. In the “Target” field at the end, append the following command line switch and click Apply.

--disable-features=RendererCodeIntegrity

Or

Change Chome executable present in this path “C:Program Files (x86)GoogleChromeApplication ” to Chrom.exe instead of Chrome.exe and see if it works.