New issue
Advanced search Search tips

Issue 876079 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 873883
Owner:
Closed: Aug 28
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

11% regression in rendering.mobile at 581775:582662

Project Member Reported by hjd@google.com, Aug 20

Issue description

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

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


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

android-nexus5x-perf
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/14e65b49640000

[PE] Stop dirtying compositing inputs on any layout for the root PaintLayer. by chrishtr@chromium.org
https://chromium.googlesource.com/chromium/src/+/46520ae13478333fe882e79041b667e5a3112796
31.77 → 36.1 (+4.333)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Mergedinto: 873883
Status: Duplicate (was: Assigned)

Sign in to add a comment