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

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


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

android-nexus6

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

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

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_news/browse_news_nytimes

Revision             Result                    N
chromium@454642      20959476 +- 31214865      21      good
chromium@454700      19627642 +- 30143275      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.news.nytimes system_health.memory_mobile

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

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


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

Weird, just this single page on this single device. Traces show java_heap allocated objects in the browser process going way up. I'll kick a bisect with no story filter on a wider range.

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

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

Please try rerunning the bisect.


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_news/browse_news_nytimes

Revision             Result                  N
chromium@454582      14865749 +- 226258      6      good
chromium@455119      27722923 +- 964471      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 system_health.memory_mobile

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

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


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

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