New issue
Advanced search Search tips

Issue 844450 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

4.2% regression in thread_times.simple_mobile_sites at 557269:557462

Project Member Reported by npm@chromium.org, May 18 2018

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, May 18 2018

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

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


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

android-webview-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 18 2018

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/14ca7ec4240000

[RLS] Don't include scroll offset for unclipped absolute bounding boxes of PaintLayers. by chrishtr@chromium.org
https://chromium.googlesource.com/chromium/src/+/7e3ce87568c3a2338775ededa458e273605da216

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
This is an expected, unfortunately required regression to achieve correctness.
It is paid for by main-frame scrolling no longer needing to update compositing
state.

Sign in to add a comment