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

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


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

android-webview-nexus5X

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

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

Hi jochen@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 : Jochen Eisinger
  Commit : 2cd2f5feff3a811eb1d2a69996f8be9f501c44a5
  Date   : Tue Mar 14 08:14:48 2017
  Subject: Remove experimental fast accessor builder API

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_tools/load_tools_docs
  Change       : 12.73% | 3298198.66667 -> 3718009.33333

Revision                           Result                  N
chromium@456689                    3298199 +- 7870.87      6      good
chromium@456690                    3299637 +- 250.354      6      good
chromium@456690,v8@97254b0d23      3340656 +- 43.8178      6      good
chromium@456690,v8@2cd2f5feff      3702585 +- 457.949      6      bad       <--
chromium@456690,v8@f52a483305      3702483 +- 480.355      6      bad
chromium@456690,v8@f20261bfb4      3702655 +- 576.934      6      bad
chromium@456691                    3717840 +- 509.494      6      bad
chromium@456693                    3717905 +- 491.127      6      bad
chromium@456697                    3717769 +- 482.715      6      bad
chromium@456705                    3717908 +- 485.007      6      bad
chromium@456720                    3718009 +- 444.906      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.tools.docs system_health.memory_mobile

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

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


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

My CL deletes unused code, it can't impact any metrics

WontFix-ing because this is 6 months old, couldn't be found, and only 300kib regression.