New issue
Advanced search Search tips

Issue 821868 link

Starred by 1 user
Status: Duplicate
Merged: issue 821409
Owner:
toyoshim@chromium.org
Closed: Mar 2018
Cc:
isherman@chromium.org
hjd@google.com
toyoshim@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.8% regression in system_health.memory_mobile at 542226:542283

Project Member Reported by hjd@google.com, Mar 14 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Mar 14 2018 

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

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


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

android-nexus5
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 15 2018

Cc: toyoshim@chromium.org isherman@chromium.org
Owner: toyoshim@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11af6cae440000

ResourceLoadScheduler: remove stale configurations by toyoshim@chromium.org
https://chromium.googlesource.com/chromium/src/+/a3d458c7e9c8ebf21833bbaa48ee4e4159a516dc

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

Comment 4 by toyoshim@chromium.org, Mar 15 2018

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

Sign in to add a comment