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

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


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

android-one

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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/background_search/background_search_google

Revision             Result                  N
chromium@475679      87576.8 +- 51542.6      21      good
chromium@475803      91389.1 +- 39026.2      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-chromium --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/8977590560099541424

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


| 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/8977581890716654224

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/background_search/background_search_google

Revision             Result                  N
chromium@475679      90494.9 +- 38708.1      21      good
chromium@475803      91176.6 +- 42758.5      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-chromium --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/8977581890716654224

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


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

This looks like noise. Long-term, this test seems to have periods of bad results, followed by periods of stability. Assigning to owner to look into fixing the test...

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

The skia regression is tiny and within noise range. Let's see if something comes out of the v8 regression.

=== 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_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background_search/background_search_google
  Change       : 6.85% | 9358105.71429 -> 9999328.88889

Revision             Result                   N
chromium@475486      9358106 +- 1493211       14      good
chromium@475512      9280981 +- 1024357       9       good
chromium@475525      9404526 +- 1040994       9       good
chromium@475527      9299013 +- 848469        6       good
chromium@475528      10413839 +- 198930       6       bad       <--
chromium@475531      10132301 +- 1437717      9       bad
chromium@475537      10219484 +- 1039639      6       bad
chromium@475587      10426094 +- 95791.8      6       bad
chromium@475687      9999329 +- 1775342       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-chromium --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/8977436378564442064

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


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