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

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


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

android-nexus6

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

 Issue 680988  has been merged into this issue.

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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/foreground/https_mobile_twitter_com_justinbieber_skip_interstitial_true

Revision             Result                    N
chromium@443032      34666922 +- 41946400      21      good
chromium@443104      37158177 +- 25527766      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=https.mobile.twitter.com.justinbieber.skip.interstitial.true memory.top_10_mobile_stress

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

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


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

This is likely due to my recent change. Investigating on other bug.

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