Chrome unresponsive on system-wake with lots of tabs but not net connection
Reported by
khym.cha...@gmail.com,
Nov 16 2016
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.100 Safari/537.36 Example URL: https://www.reddit.com/ Steps to reproduce the problem: 1. Open up at least 12 different tabs of Reddit.com content while logged in to Reddit and while there is an internet connection 2. Put computer into sleep mode 3. Wake computer up when there is no internet connection available. What is the expected behavior? All tabs can be immediately accessed. What went wrong? On my slow Windows 8.1 laptop it took around 4 to 5 minutes before the text came back to all the tabs and the browser was responsive again. Right after waking my laptop I could move easily between the various tabs, but there was no text in any of them. After a minute or two the "loading" indicators became active in most of the tabs. A minute or two after that text came back in a few of the tabs, but those tabs were unresponsive (couldn't scroll). A minute or two after *that* the text was back in all the tabs and I could scroll through all of them. Did this work before? N/A Chrome version: 54.0.2840.99 Channel: stable OS Version: 8.1 Flash Version: Shockwave Flash 23.0 r0 The extensions I have installed are Vimium, AdBlock+ and Lazarus.
,
Nov 17 2016
Are you using "sleep" (suspend-to-RAM) or "hibernate" (suspend-to-disk)? If you're unsure, it generally takes a couple seconds to enter/exit sleep mode (Where "exit" is defined by having the screen turn back on), and a couple minutes for hibernate, in my experience.
,
Nov 18 2016
,
Dec 8 2016
,
Dec 9 2016
khym...: Could you provide the information requested in c#1 & 2? WE can't make progress without your help.
,
Dec 13 2016
chrome://version and chrome://net-internals were responsive while the other tabs were spinning their wheels. Also, the Windows task manager showed that Google was maxing out the hard-drive's disk usage while the tabs were trying to reload. Attached is the result of exporting net-internals, as instructed.
,
Dec 21 2016
Thank you for providing more feedback. Adding requester "csharrison@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 21 2016
Overriding sherrifbot to put on current triagers queue.
,
Dec 21 2016
Could you try to do the same experiment in the incognito mode (i.e. with the extensions disabled) and see if the response time has improved? If the problem still exists, it will be helpful if you could collect a Chrome trace with after the system wakes up. Please go to chrome://tracing/, select 'Javascript and rendering', click on 'Edit categories' and add 'loading' & 'loader'. From the attached log, it looks that the net stack behaves correctly, i.e. the pending connections are terminated with ERR_NETWORK_IO_SUSPENDED. The new connections are failing with ERR_INTERNET_DISCONNECTED (since there is no internet connection). There are many Reddit resources (like javascript files) that are loaded from the cache. This probably contributes to high hard-drive's disk usage.
,
Dec 28 2016
Hrm...Looking at the log in comment #6, this isn't looking like a network stack issue. Every request took less than 600 milliseconds from creation to completion, except one for https://reddit.com/static/pixel.png, which took 23.8 seconds. That's presumably a tracking pixel, so presumably shouldn't affect site interactivity, and for 23.4 of those seconds, we were blocked on the renderer. Tentatively attaching the blink-loader label, though not at all confident of that.
,
Feb 2 2017
Please try incognito mode, and if you encounter the same problem, then collect Chrome trace, following instructions in comment #9. Thank you.
,
Feb 23 2017
Closing the issue due to no response from khym.chanur@. If the problem still occurs, please open a new issue and attach the trace logs as suggested in comment #9. Thank you! |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by eroman@chromium.org
, Nov 17 2016+mmenke who has been looking at suspend+network. khym.chanu: Please try running these experiments to narrow down where the problem is. Before putting the computer to sleep, open up 2 additional tabs: chrome://version/ chrome://net-internals/ Once you wake up with disconnected internet, are the version and net-internals tabs responsive? (try scrolling around in them, selecting text, and right clicking for instance). At this point, you can also switch to the net-internals window and save a net log dump (https://dev.chromium.org/for-testers/providing-network-details). Depending what that turns up, another experiment will be to capture a trace log (chrome://tracing/) while things are running slowly after wakeup. Another easy experiment would be to turn off your extensions and see if it changes anything.