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

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


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

android-nexus6

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

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

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

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


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/browse_social/browse_social_twitter


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.twitter system_health.memory_mobile

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

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


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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/browse_social/browse_social_twitter

Revision             Result                   N
chromium@469241      23203547 +- 1888817      21      good
chromium@469280      23260648 +- 1960012      21      unknown
chromium@469319      23601201 +- 1895363      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=browse.social.twitter system_health.memory_mobile

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

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


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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 5b95074ff70c578c5eef6f1201f23acec24f29c8
  bad_revision : 2277d587c39624d35fb97ea65cc610dc29a9306e

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/browse_social/browse_social_twitter
  Change       : 5.51% | 23741098.6667 -> 25048064.0

Revision             Result                  N
chromium@469319      23741099 +- 533351      6      good
chromium@469386      23688192 +- 558781      6      good
chromium@469419      23934293 +- 256784      6      good
chromium@469424      23825408 +- 641268      6      good
chromium@469426      24852480 +- 766904      6      bad
chromium@469428      24894805 +- 734674      6      bad
chromium@469436      25039189 +- 534951      6      bad
chromium@469452      25031339 +- 915649      6      bad
chromium@469585      25048064 +- 669691      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.social.twitter system_health.memory_mobile

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

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


| 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 alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.