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

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


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_news/load_news_qq

Revision             Result                 N
chromium@447503      4683971 +- 277661      21      good
chromium@447537      4681405 +- 285234      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=load.news.qq system_health.memory_mobile

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

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


| 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/8988725837435900912

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

Suspected Commit
  Author : jgruber
  Commit : d52ec9e6cfb0c5ad81d614b11957cb85fba06d96
  Date   : Wed Feb 01 08:54:38 2017
  Subject: [regexp] Store named captures on the regexp result

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_news/load_news_qq
  Change       : 1.66% | 4614931.55556 -> 4691506.66667

Revision                           Result                  N
chromium@447483                    4614932 +- 39053.9      9      good
chromium@447489                    4620576 +- 30883.4      9      good
chromium@447489,v8@0c3a507b3a      4620741 +- 22235.5      6      good
chromium@447489,v8@d52ec9e6cf      4668299 +- 95774.4      6      bad       <--
chromium@447489,v8@44cac16f48      4690209 +- 154037       6      bad
chromium@447490                    4701668 +- 213321       9      bad
chromium@447491                    4659885 +- 49349.9      6      bad
chromium@447492                    4696328 +- 186485       6      bad
chromium@447495                    4729796 +- 173906       6      bad
chromium@447507                    4699277 +- 135711       6      bad
chromium@447530                    4714843 +- 190868       6      bad
chromium@447577                    4691507 +- 167412       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=load.news.qq system_health.memory_mobile

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

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


| 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/8982620050362550432