New issue
Advanced search Search tips

Issue 713739 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 712039
Owner: ----
Closed: Apr 2017
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

On OSX Task Manager takes a lot of browser CPU.

Project Member Reported by sh...@chromium.org, Apr 20 2017

Issue description

There's the general problem of "Things are slow for no reason", which I don't think is specific to the Task Manager or OSX.  But I have noticed that when I go to the Task Manager to try to figure out if I have a tab using lots of memory or something, the browser process always seems really busy.  Eventually I took a sample, and it was mostly in updates of the Task Manager itself (I think).  I verified this by correlating with top, with the Task Manager up browser process would ping-pong between 35% and 45% CPU, but when I closed it it dropped to 10% then faded to 6-7% (I am still unhappy with that, but grumble).

I can see why this happens, but it seems like this state could cause mis-leading bug reports, etc.  I don't have any immediate suggestions on how to fix it, but my guess is that it probably doesn't get much attention, so there might be minor changes which would have an impact.
 

Comment 1 by meh...@chromium.org, Apr 22 2017

Could this be related to issue 712039 ?

Comment 2 by shrike@chromium.org, Apr 28 2017

Mergedinto: 712039
Status: Duplicate (was: Untriaged)
I believe this is Issue 712039, and my analysis there is it's expensive to compute memory metrics for a renderer, and if you have a lot of renderers you burn a lot of CPU. c#9 in that bug seems to suggest things will get better.

Sign in to add a comment