Google Confirms The Aw, Snap! Bug in Chrome 78, Here’s How You Can Fix It

Google rolled out an update for Chrome with plenty of new features on October 22. The update bumps the existing version of the browser to Chrome version 78.

The newest version seems to be problematic due to a large number of crash reports. Many people reported that they are experiencing the annoying Aw, Snap! error. Those who launched the browser after installing the update reported that they can not use the browser. Moreover, launching the browser simply leads to a page crash unexpectedly with the following message:

Aw snap! Something went wrong while displaying this webpage.

Apparently the problem affected systems running an older version of Symantec Endpoint Protection (SEP) security suite. SEP is a popular security product amongst business users. The outdated version has some incompatibility issues with a newly added feature in the recent version of Chrome.

This disruption occurs when launching the web browser on systems with an outdated version of the Symantec Endpoint Protection (SEP) security suite. Unfortunately, there are hundreds of organizations that have not upgraded yet and they are still using SEP 14.

Fix Chrome Aw, Snap Bug
Chrome 78 Error!

Incompatibility Issues

A large number of user reports forced Google and Symantec to investigate the problem. The Chrome team admitted the reports and requested the affected users to share the details regarding the problem in the help forum.

Symantec recently published a blog post to acknowledge this issue. The problem was caused due to incompatibility issues between Microsoft’s Code Integrity feature and Symantec’s Application Control technology.

As a matter of fact, the recent version of Google Chrome now renders the Code Integrity feature. This decision was made in order to “prevent unsigned modules from loading in Chrome browser’s renderer processes” in Chrome version 78 onwards.

This problem has also affected the new Microsoft Edge browser. Fortunately, the problem has a limited impact because the browser is not officially released yet.

How to Fix the Aw, Snap! Error in Chrome 78

Chrome recommends that you should install the latest version of Symantec Endpoint Protection to fix this issue. Moreover, if you are still experiencing this problem, you should disable the Renderer Code Integrity feature in Google Chrome. Follow these steps to disable the feature:

  1. Go to the Start menu and search for Google Chrome.
  2. Right-click on the Chrome icon and click Properties.
  3. Navigate to the Target field and paste the following command at the end:                                                           –disable-features=RendererCodeIntegrity
  4. Click the Apply button to save the changes.

This workaround will help you to get rid of the annoying Aw, Snap! bug in no time. Meanwhile, we hope that a permanent fix will be available very soon.


Alex Schoff

Alex is a technology reporter with a particular interest in Microsoft and Windows. He keeps a close eye on major developments related to Windows 10, Google Chrome, Office 365, and more.
Back to top button