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

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


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

android-nexus7v2
android-webview-nexus5X

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

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

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

=== Auto-CCing suspected CL author megjablon@chromium.org ===

Hi megjablon@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : megjablon
  Commit : 5e5d1c1764d4ebbad4f51ab37f1d9341e6d26efb
  Date   : Thu Apr 06 23:55:11 2017
  Subject: Create feature and enable data collection for Data Saver site breakdown

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/blank_about/blank_about_blank
  Change       : 2.46% | 10306786.6667 -> 10560580.0

Revision             Result                  N
chromium@462611      10306787 +- 125212      6      good
chromium@462677      10332048 +- 115907      6      good
chromium@462686      10333805 +- 105509      6      good
chromium@462690      10333163 +- 139625      6      good
chromium@462691      10590173 +- 106340      6      bad       <--
chromium@462692      10545191 +- 138117      6      bad
chromium@462694      10531336 +- 157056      6      bad
chromium@462710      10526980 +- 142275      6      bad
chromium@462743      10560580 +- 146829      6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=blank.about.blank system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982418169204164064

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5514608627941376


| 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 Speed>Bisection.  Thank you!