{"id":12322,"date":"2019-12-13T11:55:04","date_gmt":"2019-12-13T10:55:04","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=12322"},"modified":"2024-10-05T18:54:47","modified_gmt":"2024-10-05T16:54:47","slug":"chrome-79-das-aw-snap-problem-ist-zurck","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/12\/13\/chrome-79-das-aw-snap-problem-ist-zurck\/","title":{"rendered":"Chrome 79: Das &lsquo;AW Snap&rsquo; issue is back"},"content":{"rendered":"<p><img decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline\" src=\"http:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2015\/01\/Chrome.jpg\" align=\"left\">[<a href=\"https:\/\/www.borncity.com\/blog\/2019\/12\/13\/chrome-79-das-aw-snap-problem-ist-zurck\/\" target=\"_blank\" rel=\"noopener noreferrer\">German<\/a>]Users switching to the freshly released Google Chrome 79 browser may facing again the 'AW Snap' problem. The browser tabs are going into the \"White Screen of Death\" mode and displays the message \"Aw, Snap! Something went wrong while displaying this webpage.\" This is due to incompatible antivirus products or software tools that collide with Chrome's Code Integrity protection.<\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/vg01.met.vgwort.de\/na\/13d6e181af1c41908b68fc67e1064c4d\" width=\"1\" height=\"1\">It's kind of a zombie. At the end of October 2019, the release of Google Chrome 78 crashed under Windows. Users who had Symantec Antivirus Endpoint Protection (SEP) installed experienced a nasty surprise. Symantec Antivirus crashed the Chrome browser's browser tabs. The Microsoft Edge browser version 78, which is based on Chromium, also stopped displaying pages.<\/p>\n<p><img decoding=\"async\" title=\"Google Chrome 'Aw, Snap!'\" alt=\"Google Chrome 'Aw, Snap!'\" src=\"https:\/\/i.imgur.com\/n0LoX9l.jpg\"><br \/>(Google Chrome \"White Screen of Death\" &#8211;&nbsp; 'Aw, Snap!' message)<\/p>\n<p>The \"White Screen of Death\" page visible in the picture above with \"Aw, Snap!\" was displayed, and the tab no longer works. I had reported in the blog post <a href=\"https:\/\/borncity.com\/win\/2019\/10\/24\/symantec-antivirus-bringt-google-chrome-78-zum-absturz\/\">Symantec Antivirus crashes Google Chrome 78<\/a> about this effect. <\/p>\n<blockquote>\n<p>Furthermore, there was an experimental Chrome feature, which recently also caused these crashes (see the blog post <a href=\"https:\/\/borncity.com\/win\/2019\/11\/15\/experimentelle-chrome-funktion-verursacht-abstrze\/\">Experimental Chrome feature has caused crashes<\/a>). <\/p>\n<\/blockquote>\n<h2>The issue is back<\/h2>\n<p>On 10 December 2019, Google Chrome 79 was released (see Google Chrome 79 released). After release of the new browser version, some users are facing the \"White Screen of Death\" page with \"Aw, Snap!\" again. On Twitter there are the first references to this error. <\/p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">So Google Chrome is borked for me, I can't access anything without getting an aw snap page. Uninstalled. Try reinstalling tomorrow. <a href=\"https:\/\/twitter.com\/hashtag\/GoogleChrome?src=hash&amp;ref_src=twsrc%5Etfw\">#GoogleChrome<\/a> <a href=\"https:\/\/twitter.com\/hashtag\/Google?src=hash&amp;ref_src=twsrc%5Etfw\">#Google<\/a> <a href=\"https:\/\/twitter.com\/hashtag\/TechSupport?src=hash&amp;ref_src=twsrc%5Etfw\">#TechSupport<\/a><\/p>\n<p>\u2014 Firith (@firithpanda) <a href=\"https:\/\/twitter.com\/firithpanda\/status\/1204615470793535489?ref_src=twsrc%5Etfw\">December 11, 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script> <\/p>\n<p>The reason for the recurring issue is the Code Integrity protection in the browser that is active in Chrome 79. The colleagues at Bleeping Computer have taken this up in <a href=\"https:\/\/web.archive.org\/web\/20220811170358\/https:\/\/www.bleepingcomputer.com\/news\/google\/-aw-snap-crash-makes-a-comeback-in-chrome-79\/\" target=\"_blank\" rel=\"noopener noreferrer\">this article<\/a>. Again, incompatible software is the root cause.&nbsp; <\/p>\n<ul>\n<li>While it was an old version of Symantec Endpoint Protection (SEP) in October 2019 that caused the trouble, it appears among users who installed SEP 14.2.5323.2000.\n<li>Two users reported having the same issue with a Webroot security solution installed on their computers (the exact version of the software is unknown). However, the product has been recognized for this type of incompatibility before.\n<li>Google last time in October also <a href=\"https:\/\/support.google.com\/chrome\/thread\/17555930?hl=en\" target=\"_blank\" rel=\"noopener noreferrer\">listed<\/a> PC Matic, Print Audit and Palo Alto Traps as problematic for Code Integrity protection in the browser.<\/li>\n<\/ul>\n<p>Google released <a href=\"https:\/\/support.google.com\/chrome\/thread\/17555930?hl=en\" target=\"_blank\" rel=\"noopener noreferrer\">this support page<\/a> for Chrome 78 at the end of October 2019. It has now been updated for Chrome 79. There are hints on what to consider before upgrading to Chrome 79 (make sure antivirus products are up to date). <\/p>\n<p>I haven't tested, if the workarounds I mentioned in my blog post <a href=\"https:\/\/borncity.com\/win\/2019\/10\/24\/symantec-antivirus-bringt-google-chrome-78-zum-absturz\/\">Symantec Antivirus crashes Google Chrome 78<\/a> (e.g. run Chrome 79 in compatibility mode for Windows 8) helps. <\/p>\n<p><strong>Similar articles:<\/strong><br \/>Google Chrome 79 released<br \/><a href=\"https:\/\/borncity.com\/win\/2019\/10\/24\/symantec-antivirus-bringt-google-chrome-78-zum-absturz\/\">Symantec Antivirus crashes Google Chrome 78<\/a><br \/><a href=\"https:\/\/borncity.com\/win\/2019\/11\/15\/experimentelle-chrome-funktion-verursacht-abstrze\/\">Experimental Chrome feature has caused crashes<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]Users switching to the freshly released Google Chrome 79 browser may facing again the 'AW Snap' problem. The browser tabs are going into the \"White Screen of Death\" mode and displays the message \"Aw, Snap! Something went wrong while displaying &hellip; <a href=\"https:\/\/borncity.com\/win\/2019\/12\/13\/chrome-79-das-aw-snap-problem-ist-zurck\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[872,463,1547],"tags":[780,47],"class_list":["post-12322","post","type-post","status-publish","format-standard","hentry","category-browser","category-issue","category-software","tag-chrome","tag-issue"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/12322","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=12322"}],"version-history":[{"count":3,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/12322\/revisions"}],"predecessor-version":[{"id":35596,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/12322\/revisions\/35596"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=12322"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=12322"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=12322"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}