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

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


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

android-nexus7v2

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N    Good?
chromium@434902  3548508  22638557  120  good
chromium@434955  3553022  22402329  120  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 673342

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile
Test 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
Relative Change: 0.13%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3548
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993470252233352592


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5878177182777344

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

 Issue 673340  has been merged into this issue.

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

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

Suspected Commit
  Author : jgruber
  Commit : 4e7571a5a9bb8563ae93e0aff48c08bead765b14
  Date   : Tue Nov 29 09:03:18 2016
  Subject: [regexp] Migrate @@match to TurboFan

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/background
  Change       : 4.29% | 1883882.8 -> 1964625.33333

Revision                           Result                  N
chromium@434852                    1883883 +- 1011995      60      good
chromium@434926                    1885680 +- 1010647      60      good
chromium@434963                    1910315 +- 1016988      60      good
chromium@434972                    1912148 +- 1002012      60      good
chromium@434977                    1911918 +- 1000061      60      good
chromium@434978                    1911143 +- 2038.37      6       good
chromium@434978,v8@18eda7024b      1911899 +- 2424.0       6       good
chromium@434978,v8@9c0e2a6723      1911777 +- 2936.17      6       good
chromium@434978,v8@4e7571a5a9      1956077 +- 1686.91      6       bad       <--
chromium@434979                    1964344 +- 3068.64      6       bad
chromium@434981                    1965307 +- 1003074      60      bad
chromium@434999                    1964625 +- 1012516      60      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 memory.top_10_mobile

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

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


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