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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgnfLRugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgnYryoAoM


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

android-one

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8998355781043191808

=== Auto-CCing suspected CL author rune@opera.com ===

Hi rune@opera.com, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Implement MediaValues for initial viewport.
Author  : rune
Commit description:
  
Viewport-dependent media queries evaluate in the context of the initial
viewport when collecting @viewport rules as specified in [1]. Implement
a MediaValuesInitialViewport which returns the initial viewport
dimensions instead of the actual viewport. This change doesn't fix
 issue 332763  until we start collecting author @viewport rules before
creating RuleSets.

[1] https://www.w3.org/TR/css-device-adapt-1/#media-queries

R=timloh@chromium.org
BUG= 332763 

Review-Url: https://codereview.chromium.org/2414343002
Cr-Commit-Position: refs/heads/master@{#425628}
Commit  : cdb270396aeb667c46e53ed6df0c01fa8ddf4a74
Date    : Mon Oct 17 07:49:37 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@425623  1703936  0.0      5  good
chromium@425626  1703936  0.0      5  good
chromium@425627  1703936  0.0      5  good
chromium@425628  1716224  0.0      5  bad    <--
chromium@425633  1716224  0.0      5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 657506

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile
Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:ashmem:proportional_resident_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google
Relative Change: 0.72%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1733
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8998355781043191808


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5848059206959104

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

Looking at the graphs, I don't understand why this caused an alert. Also, they've all recovered, or it looks like it's just fluctuation.