Issue metadata
Sign in to add a comment
|
The upgrade from 32bit v 57 Chrome to 64bit v 58 causes all chrome tabs to display Aw Snap errors
Reported by
s.bar...@gmail.com,
May 8 2017
|
||||||||||||||||||||||||
Issue descriptionChrome Version : 58.0.3029.96 OS Version: 10.0 URLs (if applicable) : All (even settings does not work) Other browsers tested: N/A (Chrome issue only) What steps will reproduce the problem? 1. Random problem, most upgrades appeared to have worked successfully, however where the problem occurs the only fix is to fully de-install chrome and do a full install of 64bit (v58) chrome (enterprise installer) 2.De-installed v58 (64bit) and reinstalled (v57 32bit). The v57 version is working correctly after installation. The automatic upgrade runs, which again breaks Chrome, resulting in all tabs generating an Aw Snap error (including the settings tab) 3.The problem is related to the upgrade from 32bit to 64bit chrome. A full install of 64 bit on a clean system or after fully de-installing chrome works correctly. What is the expected result? Tabs displays rendered web pages What happens instead of that? All tabs generate the Aw Snap error (including settings) Please provide any additional information below. Attach a screenshot if possible. We've ensured EMET has been removed and all systems tested are as similar as possible. All PCs are running McAfee Enterprise (Endpoint 10.5) UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.96 Safari/537.36
,
May 8 2017
This is a known issue for McAfee's Solidcore and McAfee's DLP. Can you please try the alternative provided here- https://productforums.google.com/forum/#!topic/chrome-admins/5Tw_-fmT_QI;context-place=forum/chrome-admins Also provide us with the logs mentioned in #5 which helps in debugging - https://bugs.chromium.org/p/chromium/issues/detail?id=718464#c5
,
May 8 2017
Known McAfee bug: https://bugs.chromium.org/p/chromium/issues/detail?id=713875#c14
,
May 10 2017
Assigned to the Windows team.
,
May 18 2017
This issue looks similar to Bug ID - 713875, so merging the issue into same. Please undupe it, if anybody feel so. Thank You. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by m...@extendedreach.com
, May 8 2017