New issue
Advanced search Search tips

Issue 914796 link

Starred by 1 user
Status: Unconfirmed
Owner: ----
Cc:
fdoray@google.com
ssid@chromium.org
gab@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Jank caused by browser process background priority

Project Member Reported by etienneb@chromium.org, Dec 13 

From this slow-reports:
  5bfe73c16e4ce619

By looking to the sampled process priority we can see differents process priority:

   32 = NORMAL_PRIORITY_CLASS 
   64 = IDLE_PRIORITY_CLASS
  128 = HIGH_PRIORITY_CLASS

That means the browser process is not always to the NORMAL priority.
This is not supposed to be the case.

More examples:
  ac1940c7b67cf9ff
  544e71db51524f2e
  0e744387a92bc44a
  4540b9f957f0e1b7
  f50ccdbb868a1246
  fa4fd0ba2adc2e9d

Comment 1 by gab@chromium.org, Dec 13

Status: WontFix (was: Untriaged)
Hmmm, I can't think of anything that would change the browser process' priority from our end. If the user or third-party software is tweaking our priority there's not much we can do either... WontFix? And ignore such reports?

Comment 2 by etienneb@chromium.org, Dec 13

Status: Unconfirmed (was: WontFix)
I put back the open status.
Let have a discussion on this and get more metrics.

I mostly agree with the won't fix unless there is an easy fix that worth it.

Comment 3 by etienneb@chromium.org, Dec 14 

gab@ has a point: if the user is changing manually or by an installed program the chrome priority, we should respect it.

We need to figure out what is causing this.
►

Sign in to add a comment