Aww snap after upgrading to 58.0.3029.96 |
||||||
Issue descriptionChrome Version: 58.0.3029.96 OS: Windows Multiple users are reporting Aww snap after upgrading to 58.0.3029.96 ( (Server 08 R2 via Citrix Netscalers for remote connectivity, Server 2008R2 with Citrix XenApp 6.5.) Link to Chrome Release blog post: https://chromereleases.googleblog.com/2017/05/stable-channel-update-for-desktop.html * This loaded on some of my machines and I keep getting the "Aw, snap!" message. Nothing is loading. * I am also getting an Aw snap but from the users side on a citrix server Link to Chrome Product forums: https://productforums.google.com/forum/#!topic/chrome/ptsYxZLowxM;context-place=forum/chrome * I support 26 sites all running off centralised infrastructure (Server 08 R2 via Citrix Netscalers for remote connectivity) of which 5 have updated to the latest version last night. When first opening Chrome this morning the 5 sites received an Application error claiming it attempted to execute an illegal instruction. On closing the error Chrome starts but presents an Aww Snap page and you are unable to navigate to both webpages and settings pages within Chrome (including the extensions page). Edit: Sorry, I should probably add, we have tried the following: Reinstall Run with -incognito to rule out extensions Tried updating a test server from .81 to .86 and experienced the same error * We've got the same issue. Running Server 2008R2 with Citrix XenApp 6.5. * Some more info, we were running 32bit Chrome and according to this https://chromereleases.googleblog.com/2017/05/stable-channel-update-for-desktop.html Chrome is automatically updating to the 64 bit version for users running a 64 bit OS with 4 GB RAM or more. I've just confirmed via the chrome://help page that it has upgraded to 64 bit. The thing is though, it is still installed in the /Program Files(x86) folder, which I think may potentially be the issue. * Have just confirmed, downloading the offline x86 installer for 3029.96 and installing that resolves our issue.
,
May 3 2017
Issue 717821 has been merged into this issue.
,
May 3 2017
This s looks similar to - https://bugs.chromium.org/p/chromium/issues/detail?id=699043, please follow the instructions in comment #12.
,
May 3 2017
Yes this sounds like the same thing. For now having Chrome installed in the x86 folder regardless of bittness is expected and not the issue. Please follow the instructions in c#15 https://bugs.chromium.org/p/chromium/issues/detail?id=432595#c15 here to configure Citrix 6.5 to run the 64 bit version of Chrome properly.
,
May 3 2017
We're also seeing a large number of users reporting this issue this morning in the Chrome help forum: https://productforums.google.com/forum/#!topic/chrome/ptsYxZLowxM https://productforums.google.com/forum/#!topic/chrome/1ht9qSWq_bw https://productforums.google.com/forum/#!topic/chrome/7W1fYBbYi0Q Majority of users are reporting that it's occurring after updating to 58.0.3029.96 using Windows Server 2008 R2 and Citrix Xenapp. Users have reported that downgrading to the 32-bit version seems to temporarily fix the issue. I'll direct everyone to follow the instructions on c#15 and will follow up if I get more info or verifications.
,
May 3 2017
Reported on Reddit as well: https://www.reddit.com/r/chrome/comments/68x0zd/help_aww_snap_after_upgrading_to_580302996/
,
May 3 2017
Can we direct people to the published help center (vs crbug) as it is a bit more polished? https://support.google.com/chrome/a/answer/7380899
,
May 3 2017
Will do. Updating the forum and Reddit threads now.
,
May 3 2017
Hi, everyone experiencing issues on Citrix please consult this help article about the configuration changes required to run Chrome 64 bit on Citrix 6.5: https://support.google.com/chrome/a/answer/7380899 Some more information and discussion can be found here: https://productforums.google.com/forum/#!topic/chrome-admins/3-5s_N0fYjU Best, Julian
,
May 3 2017
,
May 3 2017
I'm seeing a lot of aww snap errors too since 58.0.3029.96 (64-bit), mainly in Gmail & Google Calendar. No issues with previous stable 58. Win7, no Citrix or remote desktop.
,
May 4 2017
Just a quick follow up that we've seen a couple of user follow ups on the forum confirming that the steps listed in c#15 and the help article has seemed to fix the issue. :)
,
May 4 2017
Re #11: This seems to be something else. Please file another bug to track that issue. Re #12: Thanks for confirming this. We have had multiple confirmations that the proposed config change fixes the problem so I am closing this bug for now.
,
May 4 2017
My enterprise has this same symptomatic issue (total lockout post upgrade 58.0.3...) for my users but not in the Citrix environment--my standalone users are experiencing it. Is there a fix yet, perhaps on another thread (that I cannot find)?
,
May 4 2017
c#11+c#13, I just opened a new issue 718464 for same issue but not in Citrix 6.5/XenApp environment
,
Jun 12 2017
My enterprise has been running Chrome v56 without issues. By group policy, auto updates for Chrome are turned off, but some people are getting automatically updated to v58 (64 bit) which is creating problems. We can't figure out how this is happening, but what is worse is that.... Chrome does not open without having to go into Task Manager to kill the process. Then it opens. I tried v59 (32 bit) and it does the same thing. What is the fix for this!!!??? Thanks. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by gov...@chromium.org
, May 3 2017Labels: Needs-Triage-M58 Needs-Bisect