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

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


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

android-webview-nexus6

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

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

Hi tzik@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 : tzik
  Commit : 70c7b36dbdba1140b672ad48d79145dd04ff5e5d
  Date   : Fri Sep 15 01:10:36 2017
  Subject: Reland of Make WTF::PassRefPtr an alias of WTF::RefPtr

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/load_games/load_games_lazors
  Change       : 1.06% | 21051600.0 -> 21275493.3333

Revision             Result                   N
chromium@502074      21051600 +- 122125       6      good
chromium@502105      21089456 +- 140870       6      good
chromium@502113      21145609 +- 87265.3      6      good
chromium@502117      21139705 +- 134682       6      good
chromium@502119      21170469 +- 106210       6      good
chromium@502120      21315229 +- 154316       6      bad       <--
chromium@502121      21287831 +- 50848.0      6      bad
chromium@502136      21275493 +- 128120       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.games.lazors system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8968030706601289616


For feedback, file a bug with component Speed>Bisection

The graph is pretty noisy, not sure if I trust that result.

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/load_games/load_games_lazors


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.games.lazors system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8968026523118227168


For feedback, file a bug with component Speed>Bisection

Lets try that one more time.

WontFixing due to noise and long time since the bug was filed.