Lots of of resource wakeups (500 wakeups per second for 90 seconds)
Reported by
kenorb@gmail.com,
May 6 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36 Steps to reproduce the problem: My Chrome is very slow (could be related to amount of tabs which I've). What I wanted to highlight, is that I've got every days couple of diagnostic files created in System Diagnostic Reports. Is that normal? Are these files useful for you? What is the expected behavior? Chrome to work more efficient. What went wrong? Periodic crashes, browser very slow (overkilling my MBP with 16GB of RAM). And I've got plenty of these diagnostic files. I've included only some of them. Did this work before? N/A Chrome version: 50.0.2661.94 Channel: stable OS Version: OS X 10.11.2 Flash Version: Shockwave Flash 21.0 r0
,
May 10 2016
500 wps is a lot but it depends on what you're doing in the browser. It would help to get a chrome://tracing trace file from the browser when it appears to be running slow.
,
May 10 2016
Which type of tracing I should generate, 'Web developer' one?
,
May 10 2016
I usually go for manual and then select all of the options.
,
May 12 2016
@kenorb: Hey, would you mind replying as per comment#4 ? Appreciate your help. Thank you!
,
May 20 2016
I think I won't be able to provide more tracing data about the performance, since I've installed bunch of extensions across my over 20-30 people profiles (which I'm using to group my tabs) to limit all the CPU background processing, which is The Great Suspender (I had already Adblock Plus to block some certain ads), so the tabs are automatically "killed" when unused for over 1h. So I think it helped with my performance issues. And I think my issue was related to large amount of tabs being open and Chrome which was processing all the JS code constantly and adverts across all the unused tabs. Before I've installed the extension, Chrome was killing my machine, in other words the problem was like in the attachments. I think without any implementation of feature which blocks the background processing (JS, gif and other animations) for unused/minimalized tabs (like The Great Suspender does), there is nothing which can help here. I think it's just a design issue and how I used to work with large amount of tabs. So I think this issue can be closed.
,
May 21 2016
Thank you for providing more feedback. Adding requester "ashejole@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
,
May 23 2016
As per comment #6 closing this issue, Please raise a new issue if you come across the similar one on latest chrome version. Thanks! |
||||
►
Sign in to add a comment |
||||
Comment 1 by rohitrao@chromium.org
, May 9 2016