Issue metadata
Sign in to add a comment
|
Chrome fails to load pages after PC wakes from sleep
Reported by
chris.wh...@cantab.net,
Aug 18 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Launch Chrome and navigate to a web page 2. Put PC into Sleep 3. Wake PC up 4. Open a new tab/window and try to navigate to a webpage (or try to reload the already-open page) What is the expected behavior? The page I attempt to navigate to after waking the PC up should load as normal. What went wrong? The page shows the loading indicator for ~ 2 minutes before finally loading the page. The tab/window in question is unresponsive during this time. Did this work before? Yes Not 100% sure but I think 58 worked OK Chrome version: 60.0.3112.101 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: I originally assumed this was a case of issue #750507 and uploaded the netlog there, but was asked to create a separate bug. From my comment on that issue: I have attached a log. The sequence of actions is: - Initially, twitter is open in a tab, everything working fine. - Start logging - Put PC into Sleep - Wake PC up - Open a new window - In the new window, navigate to Duolingo site using its thumbnail (at this point, the cached page appears and Chrome's loading indicator is spinning) - Dismiss 3 (I think) "page unresponsive" prompts, selecting "Wait" - Page eventually loads and unfreezes after a couple of minutes - Stop logging. Note also that if I attempt to close all the windows while it is in the unresponsive condition, Chrome fails to shut down properly (I get the message next time I start it up). This problem happens for me very reliably. Other browsers are not affected, and the problem only started happening a couple of months ago.
,
Sep 1 2017
Doesn't look like a proxy problem, or even a network problem from that log. (The network requests for duolingo are reasonably fast. And no proxy is being used, although a 2-3 seconds are lost due to auto-detect proxy). Based on the description, you are experiencing a hung renderer and/or browser, and this only started happening recently. I would suggest trying the following: (1) Load everything in an incognito window. Does the same problem happen now? (2) Clear your cookies and cache. Does the same problem happen now? (3) Are you running any Chrome extensions? If so, disable them all. Does the problem happen now. (4) Try running Chrome using a brand new profile, by launching it with the command line flag --user-data-dir=c:\tmpchromprofile (or some other path that doesn't exist). Does the problem happen now in this instance of Chrome?
,
Nov 29 2017
,
Dec 8 2017
I'm closing this for lack of activity. Please file a new bug if you can provide the information requested. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by mge...@chromium.org
, Aug 18 2017Status: Untriaged (was: Unconfirmed)