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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8LTZ-AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsOfapgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8MbDtQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8OmxrgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgiODbvgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8ID39QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8K7X8QkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsKeOrAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8M-0sgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8PnVswkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8IXitwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsMu99wsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsPf36ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8NmG6wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsMu99wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8MHKuwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8IXitwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8Iab_ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8Mvk4QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsK2P5goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsNrU4AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8NmG6woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8L7ivAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8Pr3sgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8Ia8ugsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8PSfpwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8KKV6AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8N6ftAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8Jn59AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8MvkoQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8MigmwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsPf3qgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8I_7vAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8Mig6wsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8J6Z5gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsKvzpQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8OSx_goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8KLv5AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8Mig6wkM


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

android-nexus6

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

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

Suspected Commit
  Author : ericrk
  Commit : 4c759d5e287eda60b6ce8708ca40a22be6436800
  Date   : Wed Jan 25 23:20:21 2017
  Subject: Temporarily disable context idle cleanup.

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/load_media/load_media_flickr
  Change       : 7614.66% | 177712.0 -> 13709872.0

Revision             Result                  N
chromium@446145      177712 +- 0.0           6      good
chromium@446159      177712 +- 0.0           6      good
chromium@446160      177712 +- 0.0           6      good
chromium@446161      13805315 +- 505864      6      bad       <--
chromium@446163      13709872 +- 0.0         6      bad
chromium@446166      13802715 +- 508520      6      bad
chromium@446173      13802715 +- 508520      6      bad
chromium@446201      13709872 +- 0.0         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=load.media.flickr system_health.memory_mobile

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

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


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

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

Suspected Commit
  Author : ericrk
  Commit : 4c759d5e287eda60b6ce8708ca40a22be6436800
  Date   : Wed Jan 25 23:20:21 2017
  Subject: Temporarily disable context idle cleanup.

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/load_media/load_media_flickr
  Change       : 7614.66% | 177712.0 -> 13709872.0

Revision             Result                  N
chromium@446145      177712 +- 0.0           6      good
chromium@446159      177712 +- 0.0           6      good
chromium@446160      177712 +- 0.0           6      good
chromium@446161      13805315 +- 505864      6      bad       <--
chromium@446163      13709872 +- 0.0         6      bad
chromium@446166      13802715 +- 508520      6      bad
chromium@446173      13802715 +- 508520      6      bad
chromium@446201      13709872 +- 0.0         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=load.media.flickr system_health.memory_mobile

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

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


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