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

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


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

android-nexus7v2
android-nexus9

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

=== Auto-CCing suspected CL author junov@chromium.org ===

Hi junov@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : junov
  Commit : 41d279a5476937a3981a8413be722d42da0de0d2
  Date   : Mon Jan 16 18:13:50 2017
  Subject: Add an heuristic for promoting canvases to GPU acceleration

Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/browse_news/browse_news_flipboard
  Change       : 44.47% | 101661282.667 -> 146874009.0

Revision             Result                     N
chromium@443879      101661283 +- 11404528      6      good
chromium@443912      98789166 +- 7255913        6      good
chromium@443920      98968362 +- 15119832       6      good
chromium@443922      101627350 +- 10725920      6      good
chromium@443923      148144895 +- 17671704      6      bad       <--
chromium@443924      141422512 +- 18831155      6      bad
chromium@443928      145241586 +- 26386859      6      bad
chromium@443944      146874009 +- 19131767      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=browse.news.flipboard system_health.memory_mobile

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

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


| 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 bug has an owner, but was in a state that our triage picked up. Marking as Assigned.

This is super old. Looking at the CL description, it's likely just shifting memory, WontFix-ing.

This is super old. Looking at the CL description, it's likely just shifting memory, WontFix-ing.