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

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


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

android-webview-nexus6

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

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

Hi lfg@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 : Lucas Furukawa Gadani
  Commit : 8b4643f67dc1c6b142a152aa2b76c771287e3a22
  Date   : Wed Jun 28 06:22:23 2017
  Subject: Fix crash when changing blink settings to enable plugins.

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:private_dirty_size_avg/background/after_http_www_baidu_com_s_word_google
  Change       : 2.04% | 41635576.0 -> 40785656.0

Revision             Result                  N
chromium@482896      41635576 +- 673241      6      good
chromium@482902      41801464 +- 576089      6      good
chromium@482903      40006733 +- 503147      6      bad       <--
chromium@482904      40823203 +- 418461      6      bad
chromium@482905      40711245 +- 428406      6      bad
chromium@482907      40785656 +- 606782      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 memory.top_10_mobile

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Christopher Cameron
  Commit : 1894d423068be735560e0171922c833c4091b5d1
  Date   : Wed Jun 28 06:31:03 2017
  Subject: color: Enable color correct rendering by default

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:private_dirty_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science
  Change       : 1.52% | 57842765.3333 -> 58722722.6667

Revision             Result                  N
chromium@482896      57842765 +- 828515      6      good
chromium@482902      57855053 +- 436812      6      good
chromium@482903      58027085 +- 362556      6      good
chromium@482904      58928888 +- 469023      6      bad       <--
chromium@482905      58877005 +- 318682      6      bad
chromium@482907      58722723 +- 583868      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 memory.top_10_mobile

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

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


For feedback, file a bug with component Speed>Bisection