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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgpoSv9AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxozYrggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghtPOiAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgpsKnpAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxq6E1wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxt6lhAgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxuL87AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxt3rrAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxsuntAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxtqU_QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxqGciAgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxuzymQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxrT40QkM


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

android-nexus5X
android-webview-nexus5X

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_social/browse_social_facebook


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=browse.social.facebook system_health.memory_mobile

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

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


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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_social/browse_social_facebook


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=browse.social.facebook system_health.memory_mobile

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

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


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

Restarted this, failed due to  crbug.com/728594 

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

Suspected Commit
  Author : khushalsagar
  Commit : 4e1be6ae8914f0eeed1df004b74a467bcb93241b
  Date   : Wed May 31 21:45:49 2017
  Subject: cc: Enable perf testing for checker-imaging.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_media/browse_media_facebook_photos
  Change       : 39.30% | 33042170.6667 -> 46026669.3333

Revision             Result                    N
chromium@476023      33042171 +- 7984933       6      good
chromium@476032      34521859 +- 10063033      6      good
chromium@476037      31952731 +- 2017825       6      good
chromium@476039      31627781 +- 238004        6      good
chromium@476040      33042171 +- 7984933       6      good
chromium@476041      48694643 +- 7984933       6      bad       <--
chromium@476058      48430896 +- 6763923       6      bad
chromium@476092      47297557 +- 2920402       6      bad
chromium@476161      46026669 +- 3313252       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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.facebook.photos system_health.memory_mobile

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

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


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