Google disables Renderer Code Integrity feature in Chrome 78 after Aw, Snap! Crashes

Apart from Symantec Endpoint Protection, Google has found Chrome’s new security feature Renderer Code Integrity on Windows is incompatible with three other applications, to further avoid crashes in the Chrome browser the company has disabled the security feature and said it will work with these application vendors to improve the feature compatibility. Google says the feature will be re-enabled in future versions of Chrome when the issues are sorted out.

Here is what happened:

Recently Google has shipped Chrome 78 for Windows, Mac, Linux platforms. Chrome’s new version came with the Renderer Code Integrity security feature enabled by default on Windows 10. After installing the update, Chrome users reported browser is showing Aw, Snap! Crash messages when they launch the browser.

Chrome team has acknowledged there is a compatibility issue with Symantec Endpoint Protection and aksed affected users using that to update to the latest version 14.2. The Chromium team after gathering information from users in the support forum found there more applications are not compatible with the feature.

“We are investigating reports of incompatibilities with the applications listed below. You can follow along with each of them with the development bug provided.” Chrome Support Manager, Craig said in the Help forum.

PC Matic |https://crbug.com/1017220

Print Audit | https://crbug.com/1017982

Palo Alto Traps | https://crbug.com/1018941

The security feature that has incompatibilities with other applications has been disabled for now, the feature will be re-enabled in the future, meanwhile, the Chrome team asks users using said incompatible applications to contact their vendors for timelines for the fix.

We have temporarily disabled the new Chrome feature that is resulting in the incompatibility while we partner with these software providers to improve compatibility. If you were affected by the incompatibility of a product listed above, please contact the application’s provider to understand their timelines for a fix.