Freeze after resume from suspend
Reported by
davidawehr@gmail.com,
Sep 20 2017
|
|||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0 Steps to reproduce the problem: 1. Have Chrome open 2. Put computer to sleep (standby) 3. Resume computer from sleep What is the expected behavior? Chrome is able to browse as normal What went wrong? For about 30 seconds immediately after resume, I can use Chrome as normal. After that time, new pages will not load, but the main UI remains responsive. Sometimes pages will become totally unresponsive, and scrolling does not work. After about 2 minutes, pages become responsive again and links load. Did this work before? Yes Chrome version: 61.0.3163.91 Channel: stable OS Version: 10.0 Flash Version: 27.0.0.130 I have uninstalled Chrome and deleted the ~\AppData\Local\Google\Chrome\Default folder to clear the profile before reinstalling, and this still happens. Network connectivity is fine as other browsers work. Issue appeared sometime around June. chrome://crashes/ is empty
,
Sep 25 2017
@ davidawehr-- Thanks for the report.. Unable to reproduce the issue on windows 7 & 10 using chrome latest stable M61 #61.0.3163.100 and latest canary M63 #63.0.3222.0 . @ Could you please updated your chrome to latest stable and try in a fresh chrome profile without any extensions and flags enabled and update us with your observations. Thanks!
,
Oct 17 2017
Removing from the bisect queue since we are not able to repro.
,
Nov 22 2017
This happens on my laptop as well, it's extremely annoying. It may have to do with the hardware or whatever. OS: Windows 10 Chrome: 63.0.3239.52 (Official Build) beta (64-bit) (and dev, and stable) System: ASUS g750jz Basically, what OP says. You put your laptop into suspend, and then resume in whatever time. Does not matter if you just put it into a 5 second, or 5 year sleep. Once it comes back, Chrome does not work. You can open tabs, but nothing loads. Like it's waiting for the HDD/SSD, it kinda looks like an IO wait or something. I always go "hmm Windows takes some time until it has internet connection, didn't they say it will be so fast?" And then I just open Firefox or IExplore and they both can browse right off the bat. Is there any way I could help you guys debug/trace this?
,
Nov 22 2017
By the way: OS Build: 16299.64 Anti-virus: NOD32 LAN is "Atheros AR8171/8175", but it happens both from wifi (Killer N1202) too. You can look up the specs for the laptop by model number.
,
Nov 22 2017
If you guys let me know how to debug more, I will run more tests. Like I just did a quick suspend (few seconds) and there was no hang. It might take some time. I will keep posting here with more observation.
,
Nov 22 2017
I consistently reproduce this problem on 2 different machines. I've captured an ETW trace with Bruce Dawson's UI for ETW, I can share it privately if it helps get this issue fixed.
,
Jan 1 2018
I recently purchased a new laptop, and am still experiencing the same issue. I have attached a trace that I recorded with about:tracing. This is with: - A fresh install of the latest Chrome (version 63.0.3239.108), not signed in, with my User Data directory deleted before installing. - Windows 10 Pro, Version: 1709, Build: 16299.125
,
Jan 1 2018
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 3 2018
Unable to reproduce the issue on reported chrome version 61.0.3163.91 and latest stable 63.0.3239.108 using Windows-10 HP ELITEBOOK Adding the component as Internals>Core for further triaging this issue Thanks!
,
Jan 3 2018
,
Jan 18 2018
As per comment#2 and #10 unable to reproduce this issue from TE end. Hence adding TE-NeedsTriageHelp label. Could someone from Internals>Core team please have a look at this issue. Thanks!
,
Mar 12 2018
@eroman, @mmenke - do you think this is same as issue 770201 ?
,
Mar 12 2018
In my case (original report), this seems to be the same as issue 770201 . I have some virtual network adapters, and disabling the Windows auto-detect proxy setting resolves the issue. Thanks for pointing that out, @kochi! |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by nyerramilli@chromium.org
, Sep 22 2017