Issue metadata
Sign in to add a comment
|
Chrome 58.0.3029.96 user interface is unusable - extremely slow in updating
Reported by
ayman.ca...@gmail.com,
May 7 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.96 Safari/537.36 Steps to reproduce the problem: As far as I know 1. Open the browser 2. Open around 1400 tabs with the Tab Suspender and Session Buddy extensions installed with all tabs suspended 3. Use the User Interface What is the expected behavior? The user interface used to work absolutely fine with these conditions. Even though I had 1400 tabs open, the interface, as well as the tab content, worked swiftly and instantly, thanks to the use of these extensions. What went wrong? The UI is unusable. Every single action on the UI takes several seconds, sometimes at least 10, to register on the screen and perform. This includes switching tabs, writing in the address bar and clicking every other menu and button on the UI. The tab content however, i.e. the webpages, works at normal speed. It is likely that the UI is delayed in updating rather than performing, because text entered in the address bar while frozen will still fully show up afterwards. Did this work before? Yes The release version which exactly preceded Chrome 58.0.3029.96 Chrome version: 58.0.3029.96 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 25.0 r0 This issue occurred as a result of Chrome's policy of forced upgrades and lack of a method to downgrade Chrome. If that repetitive warning to update hadn't appeared in my Chrome menu, forcing me to upgrade when the browser relaunches, this issue would've never happened.
,
May 30 2017
ayman.campbell@ Could you please confirm are you still facing this issue on latest chrome? Please try to upgrade chrome to latest stable 58.0.3029.110 and beta 59.0.3071.71 and check the issue on new profile without any extensions/flags.Please update the thread if the issue still persists. Thanks,
,
Dec 13 2017
Are you still surviving with 1400 tabs? My experience with lots of tabs is that when I restart Chrome (update or not), the tabs will fetch new versions of web pages. Sometimes those web pages are coded badly, and often I can end up with one with bad javascript that eats CPU perpetually. If you're still experiencing something like this, or see this again, please go into Tools -> Task Manager and check the CPU column to see if the problem is a particular tab or the "Browser" process itself.
,
Dec 13 2017
You can switch to CentBrowser, a fork of Chrome, which starts in half a second with all tabs suspended initially. The option is "Enable lazy session loading" in "On startup" section of browser settings.
,
Dec 14 2017
Apologies for not seeing these replies earlier. I have maintained my browser at around 300–400 tabs since the disruptive update in May 2017. Delays have been unnoticeable at this number of tabs. I have not tested bringing my number of tabs back to 1,400 again, but I can only assume the issue will occur again. I'm not in need of testing it again and risking the loss of functionality and probably my tab session too in my Chrome browser; I am happy with the 300–400 tabs I have now. I am now on version 62.0.3202.89, but an update has been pending for a while. I hope you understand that in my Chrome browser, there was absolutely no issue before the April/May 2017 update to version 58.0.3029.96. The issue started upon the installation of this update and the reopening of Chrome with this version. Thank you for your assistance.
,
Dec 14 2017
Thank you for providing more feedback. Adding requester "kavvaru@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
,
Dec 14 2017
Thanks for the feedback. I'll close this bug for now. (I don't think anyone wants to go hunting Chrome 58 to find out what changed.) We generally know that managing many tabs is hard. And we know that some people who try to do so use some sort of fork or extension or something to help (pause/suspend tabs, etc.). The Chrome team is actively thinking about how to make this area better. I don't think there's a need to keep this particular bug open though.
,
Dec 14 2017
(it may help to know which version Chrome is trying to update me to while an update is pending) |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ranjitkan@chromium.org
, May 12 2017