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

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

Suspected Commit
  Author : nednguyen
  Commit : e80a730b1b1b43ec5fa205dd99e5f00693173f4c
  Date   : Fri Apr 28 09:26:12 2017
  Subject: [Telemetry] Switch Android platform to no longer uses test ca

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_avg/browse_news/browse_news_washingtonpost
  Change       : 20.03% | 9130327.2723 -> 10959505.8328

Revision                                 Result                   N
chromium@467921                          9130327 +- 986629        6      good
chromium@467939                          8872152 +- 243215        6      good
chromium@467948                          8882889 +- 175856        6      good
chromium@467952                          9103765 +- 407809        6      good
chromium@467953                          8957460 +- 346133        6      good
chromium@467953,catapult@e80a730b1b      11108246 +- 675533       6      bad       <--
chromium@467954                          11050403 +- 804528       6      bad
chromium@467956                          11192271 +- 959668       6      bad
chromium@467991                          10959506 +- 1237347      6      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.news.washingtonpost v8.browsing_mobile

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

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


| 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 Speed>Bisection.  Thank you!