all tabs freeze after hibernate
Reported by
shadox...@gmail.com,
Dec 5
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0 Steps to reproduce the problem: 1. open many tabs 2. hibernate your pc 3. wake it up again What is the expected behavior? The state of chrome is the same as before hibernating. What went wrong? All chrome windows are completely frozen - don't open at all or are just plain white for quite some time. Often the freeze fixes itself after ~30min, but sometimes I wait for hours and nothing changes. Did this work before? N/A Chrome version: current Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 17.0 r0 One of the chrome processes is at 13% cpu in task manager (4c hyperthreading -> 13% = maximal usage of single thread), while all other are mostly 0%, once in a while for a second 1%. The running process seems to be the main one - the cmd line included nothing but a website link, while all other processes have a "type=..." argument.
,
Dec 12
Thanks for filing the issue... Unable to reproduce the issue on reported chrome version 71.0.3578.80 using Windows 10. Attaching screen-cast for reference. Steps: ------ 1. Launched chrome 2. Opened many tabs and changed pc to hibernate mode 3. Opened pc As we have observed that the state of chrome is the same as before hibernating. @Reporter: Request you to retry this issue with fresh profile without any extensions & apps or reset all the flags and let us know if issue still persists.Verify the issue on latest chrome 71.0.3578.98, The latest chrome builds can be downloaded from the below url: https://www.chromium.org/getting-involved/dev-channel and let us know if the issue still persists. Thanks.!
,
Dec 12
I think the issue only occurs when there is almost no available ram and the cached web pages take a lot more space than is free. The websites that are currently open might also be relevant - supposedly multiple scripts fighting over memory while catching up the frozen time might be a reason for the high cpu usage of the primary chrome process. Sadly reproducing spontaneously is difficult: if opening random websites didn't do the job, I would have to keep many tabs open during normal use, risking data loss if the issue did happen again. If I encounter the issue next time, I will upload screenshots/memory dumps/log files as required. What exactly do you need to pin down the cause of the issue?
,
Dec 12
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 8
@reporter: Could you please provide screencast and log files of the issue, so that it would be really helpful in triaging the issue. Thanks.! |
||||
►
Sign in to add a comment |
||||
Comment 1 by viswa.karala@chromium.org
, Dec 6