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

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


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

android-nexus7v2
android-nexus9

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@439786  88381517  2734183  21  good
chromium@439847  88358062  3070860  21  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 677427

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.media.flickr system_health.memory_mobile
Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_media/load_media_flickr
Relative Change: 0.03%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2343
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8991948591293518768


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5807108375707648

| 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 Tests>AutoBisect.  Thank you!

Blocking on  crbug.com/671156  for no-repro on system_health.memory_mobile. Using --story-filter affects reproducibility on this benchmark, try running without it.

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

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

Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_media/load_media_flickr

Revision             Result                   N
chromium@439786      88381517 +- 2734183      21      good
chromium@439847      88358062 +- 3070860      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=load.media.flickr system_health.memory_mobile

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

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


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