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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgiLDOoQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8O2itAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsMe18QkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8PL_tQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8PKbpAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgiKK1swkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsMeItgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsOm_mgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8OaSvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8K3z6QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8PL_tQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8JnulQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8IWpvwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8K3zqQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8PKbpAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgiPDwpQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8PKbpAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8LqC7gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8K-xqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8PrjowsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgiPDLsgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8L6pigsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8JK-nggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8K2avwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8PKNuQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8NqQnAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsJ6H_QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsKvQ_wgM


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

android-nexus5X
android-nexus9

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

 Issue 686145  has been merged into this issue.

2017-01-27 19:50:32 
=== 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_nexus9_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/foreground/https_mobile_twitter_com_justinbieber_skip_interstitial_true
  Change       : 41671.13% | 144620.0 -> 60409413.0

Revision             Result               N
chromium@446112      144620 +- 0.0        6      good
chromium@446155      144620 +- 0.0        6      good
chromium@446158      144620 +- 0.0        6      good
chromium@446160      144620 +- 0.0        6      good
chromium@446161      60409413 +- 0.0      6      bad       <--
chromium@446166      60409413 +- 0.0      6      bad
chromium@446176      60409413 +- 0.0      6      bad
chromium@446197      60409413 +- 0.0      6      bad
chromium@446282      60409413 +- 0.0      6      bad
chromium@446451      60409413 +- 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=https.mobile.twitter.com.justinbieber.skip.interstitial.true memory.top_10_mobile

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

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


| 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_nexus9_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/foreground/https_mobile_twitter_com_justinbieber_skip_interstitial_true
  Change       : 41671.13% | 144620.0 -> 60409413.0

Revision             Result               N
chromium@446112      144620 +- 0.0        6      good
chromium@446155      144620 +- 0.0        6      good
chromium@446158      144620 +- 0.0        6      good
chromium@446160      144620 +- 0.0        6      good
chromium@446161      60409413 +- 0.0      6      bad       <--
chromium@446166      60409413 +- 0.0      6      bad
chromium@446176      60409413 +- 0.0      6      bad
chromium@446197      60409413 +- 0.0      6      bad
chromium@446282      60409413 +- 0.0      6      bad
chromium@446451      60409413 +- 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=https.mobile.twitter.com.justinbieber.skip.interstitial.true memory.top_10_mobile

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

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


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