New issue
Advanced search Search tips

Issue 808630 link

Starred by 1 user
Status: Duplicate
Merged: issue 808629
Owner:
bsalo...@google.com
Closed: Feb 2018
Cc:
robertph...@google.com
npm@chromium.org
bsalo...@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2% regression in memory.top_10_mobile at 532458:532527

Project Member Reported by npm@chromium.org, Feb 2 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Feb 2 2018 

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

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


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

android-webview-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Feb 3 2018

Cc: bsalo...@google.com robertph...@google.com
Owner: bsalo...@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16d08abe840000

Reenable GrTextureOp antialiasing. by bsalomon@google.com
chromium @ 76a4d4d3c761cea62266bf8d1141b0d8ac84a60b

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

Comment 4 by bsalo...@google.com, Feb 5 2018

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

Sign in to add a comment