New issue
Advanced search Search tips

Issue 873382 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 872172
Owner:
Closed: Aug 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

8.5%-47.1% regression in rendering.mobile at 580992:581340

Project Member Reported by lanwei@chromium.org, Aug 10

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=873382

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


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

Android Nexus5X WebView Perf
mac-10_12_laptop_low_end-perf
Cc: rmcilroy@chromium.org
Components: -Blink>JavaScript Blink
The regression range does not show a V8 change. Ross, any clue?
Cc: -rmcilroy@chromium.org sadrul@chromium.org vmi...@chromium.org
Not sure why we think this is V8, looks like it is regressing a rendering metric.  Adding benchmark owners and kicking off a bisect.
Cc: chrishtr@chromium.org
Owner: chrishtr@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12b13b06640000

Only invalidate property trees and compositing for PaintLayers when needed, on style change. by chrishtr@chromium.org
https://chromium.googlesource.com/chromium/src/+/ba8c87a1a32815e6061b7c38d31ddfbbaac7a124
10.21 → 14.74 (+4.532)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Components: -Blink Blink>Compositing
Mergedinto: 872172
Status: Duplicate (was: Assigned)

Sign in to add a comment