Google Update via proxy causing Aw-snap error and unresponsive browser
Reported by
krish...@gmail.com,
Oct 27 2017
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3; rv:11.0) like Gecko Steps to reproduce the problem: 1.Install Google Chrome Version 60.0.3112.113 on a Windows 2008 R2 Server. 2.Go To Help->About Google Chrome 3.It will trigger an update to Google Chrome and prompt to Relaunch the Browser. 4. Relaunch the Chrome Browser 3. What is the expected behavior? It should Relaunch the Browser successfully and we should be able to browse the websites. What went wrong? On Relaunching the browser it shows "Aw, Snap" Error Unable to browser any websites or even the "Chrome://" urls (e.g.chrome://settings/help). Also Chrome browser is freezing up and eventually will say page stopped responding, would you like to kill it Crashed report ID: No How much crashed? Whole browser Is it a problem with a plugin? N/A Did this work before? N/A Chrome version: 60.0.3112.113 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Oct 27 2017
,
Oct 30 2017
One more information that needs to be taken into account is that the Windows 2008 R2 Server is used as a Citrix Server (Version 6.5)
,
Oct 30 2017
,
Oct 30 2017
,
Oct 30 2017
GoogleUpdate.log indicates that the update from 60.0.3112.113 to 61.0.3163.100 succeeded. Do you have the same problem with a fresh install of Chrome 61? +pastarmovj who has done work to get Chrome running under Citrix.
,
Oct 30 2017
The version is getting updated but the browser is rendered unusable because of Aw, snap error. Thanks & Regards, Krishnaraj.V Mobile : +91 9535100864 "Success is not final, failure is not fatal: it is the courage to continue that counts" “Truth doesn’t get you many friends but it does get you the right ones” “Yesterday is gone. Tomorrow has not yet come. We have only today. Let us begin.”
,
Oct 31 2017
Unable to triage this issue from TE-End because of lack of Proxy setup, hence adding TE-NeedsTriageFromMTV label for further triage
,
Nov 2 2017
Hello can you please check in the User Data folder of Chrome under if any crashes were stored in the crashpad folder? If so please send the most recent ones per email to pastarmovj at chromium.org if you don't wish to upload some on this publicly visible bugs. I don't see any particular errors in the log files uploaded.
,
Nov 17 2017
Any luck finding some crash reports?
,
Oct 29
Archiving, no recent activity |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by krish...@gmail.com
, Oct 27 2017