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

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


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

android-one

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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : v8.browsing_mobile_ignition
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:code_and_metadata_size_avg/browse_social/browse_social_twitter

Revision             Result                  N
chromium@442252      1186685 +- 58462.2      21      good
chromium@442341      1198323 +- 69487.3      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 --story-filter=browse.social.twitter v8.browsing_mobile_ignition

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

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


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

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