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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6MrZuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6MyEvgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6Jv9uQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6MrkogkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6JHXrwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqMOntAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6Ir_vQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6O-xpAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6PSkqQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6JHXrwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6La2vgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqOH69woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqN_vtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqLu76ggM


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

android-one

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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/background/after_http_m_youtube_com_results_q_science

Revision             Result                   N
chromium@448079      25152739 +- 2680921      21      good
chromium@448497      25580088 +- 2698631      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=http.m.youtube.com.results.q.science memory.top_10_mobile

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

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


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

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

 Issue 690990  has been merged into this issue.

=== 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_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science

Revision             Result                  N
chromium@448079      40370257 +- 823662      14      good
chromium@448497      41308533 +- 344155      14      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 memory.top_10_mobile

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

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


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

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.