New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 812320 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

17.5%-24.8% regression in system_health.common_desktop at 536274:536343

Project Member Reported by fmea...@chromium.org, Feb 14 2018

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Feb 14 2018

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=812320

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=963bbad8a769ab80329b9221adfc5002c95dae1829bbc0ecd876d2c0cb8bf2e0


Bot(s) for this bug's original alert(s):

chromium-rel-win10
chromium-rel-win8-dual
This is probaly due to the Revert in https://chromium-review.googlesource.com/c/chromium/src/+/915130

If the bisect agrees, please close as WontFix.

Thanks.
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Feb 14 2018

Cc: chrishtr@chromium.org skobes@chromium.org
Owner: skobes@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1495f603840000

Revert "Enable root layer scrolling." by skobes@chromium.org
https://chromium.googlesource.com/chromium/src/+/066296a5708f57ba89b68605ae8e65292eb77d4d

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
The blame is pointing to a revert CL, marking as WontFix
Issue 812314 has been merged into this issue.
 Issue 812393  has been merged into this issue.
 Issue 812391  has been merged into this issue.
 Issue 812388  has been merged into this issue.
 Issue 812382  has been merged into this issue.
 Issue 812312  has been merged into this issue.
Cc: briander...@chromium.org
 Issue 814050  has been merged into this issue.

Sign in to add a comment