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

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


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

android-webview-nexus6

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

=== 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_chrome:cc:effective_size_avg/background_search/background_search_google

Revision             Result                    N
chromium@475478      37986955 +- 42168606      21      good
chromium@475504      40772235 +- 44670741      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=background.search.google system_health.memory_mobile

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

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


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

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

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

=== 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_chrome:cc:effective_size_avg/background_search/background_search_google

Revision             Result                    N
chromium@475478      36183934 +- 38567085      21      good
chromium@475504      37922589 +- 41764131      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=background.search.google system_health.memory_mobile

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

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


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

Filed bug 730136, since dashboard results strongly disagree with bisect results.

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

Suspected Commit
  Author : hiroshige
  Commit : 67e066b84ec7953ec06ecf252f466c2c2c063f33
  Date   : Tue May 30 15:09:31 2017
  Subject: Reland of remove EventSender from ImageLoader (patchset #1 id:1 of https://codereview.chromium.org/2903773002/ )

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:cc:effective_size_avg/background_search/background_search_google
  Change       : 45.31% | 37135181.7143 -> 49154926.2222

Revision             Result                    N
chromium@475445      37135182 +- 32387719      14      good
chromium@475504      35623758 +- 29704091      14      good
chromium@475522      34285536 +- 25717572      14      good
chromium@475526      35705385 +- 30283342      14      good
chromium@475527      36122494 +- 38057255      21      good
chromium@475528      49637637 +- 4073515       14      bad       <--
chromium@475530      49797543 +- 3253851       9       bad
chromium@475537      50235360 +- 2660427       14      bad
chromium@475566      49511246 +- 3885618       14      bad
chromium@475686      49154926 +- 3030120       9       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=background.search.google system_health.memory_mobile

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

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


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