New issue
Advanced search Search tips

Issue 876018 link

Starred by 1 user
Status: Duplicate
Merged: issue 873883
Owner:
chrishtr@chromium.org
Closed: Aug 21
Cc:
hjd@google.com
chrishtr@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

179.1% regression in rendering.mobile at 581775:582662

Project Member Reported by hjd@google.com, Aug 20 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 20 

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

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


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

android-nexus5x-perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 21

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/1192f3d6640000

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

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 4 by chrishtr@chromium.org, Aug 21

Mergedinto: 873883
Status: Duplicate (was: Assigned)
►

Sign in to add a comment