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

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


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

android-nexus9

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

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

Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : v8.browsing_mobile_turbo
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg

Revision             Result                   N
chromium@445215      19281854 +- 2550749      21      good
chromium@445273      19416531 +- 2506446      21      bad

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 v8.browsing_mobile_turbo

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

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


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

Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.