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

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


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

android-webview-nexus6

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_news/load_news_irctc

Revision             Result                   N
chromium@501243      38161625 +- 1288569      21      good
chromium@501271      38282360 +- 1277658      21      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.irctc 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/8968386720999328656


For feedback, file a bug with component Speed>Bisection

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

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

Hi jgruber@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 : Jakob Gruber
  Commit : 150fd5925497793ac421cdf951de8abec0e5cf04
  Date   : Tue Sep 12 07:12:12 2017
  Subject: Revert "Reland "[snapshot] Temporarily enable --lazy-deserialization""

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_news/load_news_irctc
  Change       : 2.19% | 37420021.7778 -> 38238084.0

Revision                           Result                   N
chromium@501230                    37420022 +- 897254       9      good
chromium@501230,v8@150fd59254      38081981 +- 1140373      9      bad       <--
chromium@501230,v8@745ae2d8d7      38148655 +- 749074       6      bad
chromium@501231                    38249007 +- 677877       6      bad
chromium@501232                    38266756 +- 440924       6      bad
chromium@501233                    38018948 +- 380410       6      bad
chromium@501236                    38097227 +- 1410048      9      bad
chromium@501241                    38169476 +- 448086       6      bad
chromium@501251                    38056665 +- 782421       6      bad
chromium@501271                    38238084 +- 600054       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.irctc 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/8960842201317144272


For feedback, file a bug with component Speed>Bisection

Bisects to a revert that has since been relanded, closing.