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

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


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

android-webview-nexus5X

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

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

Hi danno@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 : danno
  Commit : e466744da5a51fefbec5357a35a17b8fffe987b2
  Date   : Thu Mar 09 14:40:02 2017
  Subject: [interpreter] Create custom call opcodes for specific argument counts

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/load_news/load_news_flipboard
  Change       : 3.99% | 11863464.0 -> 12336392.0

Revision                           Result                   N
chromium@456045                    11863464 +- 115874       6      good
chromium@456048                    11855955 +- 102610       6      good
chromium@456048,v8@fa7b88fddd      11844019 +- 158803       6      good
chromium@456048,v8@99bdf971c8      11827255 +- 46251.7      6      good
chromium@456048,v8@0ca72de24c      11847339 +- 76213.7      6      good
chromium@456048,v8@18be5d7057      11836036 +- 45269.1      6      good
chromium@456048,v8@e466744da5      12371671 +- 41809.0      6      bad       <--
chromium@456049                    12354481 +- 35491.8      6      bad
chromium@456050                    12382381 +- 108180       6      bad
chromium@456054                    12385952 +- 109078       6      bad
chromium@456062                    12336392 +- 91015.9      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.flipboard system_health.memory_mobile

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

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


| 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!

The graphs have recovered since the original regression.