New issue
Advanced search Search tips

Issue 844603 link

Starred by 1 user
Status: WontFix
Owner:
chrishtr@chromium.org
Closed: May 2018
Cc:
npm@chromium.org
chrishtr@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.8%-19% regression in memory.top_10_mobile at 558300:558760

Project Member Reported by npm@chromium.org, May 18 2018 
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=844603

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


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

android-one
linux-perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 19 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/12ca7ec4240000

Apply fixed-position scroll offset if the containing block is ancestor. by chrishtr@chromium.org
https://chromium.googlesource.com/chromium/src/+/edc066c316b24fb3dea226ae6c1c5c1fdee062c3

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

Comment 4 by chrishtr@chromium.org, May 20 2018

Status: WontFix (was: Assigned)
This is really a revert of https://chromium.googlesource.com/chromium/src/+/e931d2aecb4d72946962e57e7e1586668071b504.
►

Sign in to add a comment