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

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


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

android-webview-nexus6

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

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

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

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: f94a806ba1b6108745375cde099fd402c536281d
  bad_revision : 110d2edcc9f18a0d689708a00d67102df9dc8521

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : v8.mobile_infinite_scroll_tbmv2
  Metric       : v8-gc-scavenger_max/discourse
  Change       : 26.79% | 16.1826666667 -> 20.5175

Revision             Result                  N
chromium@481581      16.1827 +- 3.50074      6      good
chromium@481592      20.1602 +- 1.10503      6      bad
chromium@481603      20.5175 +- 2.08253      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=discourse v8.mobile_infinite_scroll_tbmv2

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

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


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

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

=== Auto-CCing suspected CL author ulan@chromium.org ===

Hi ulan@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : 5d8840e24e0e98136c081ee22441d808412d06e2
  Date   : Thu Jun 22 12:37:26 2017
  Subject: [runtime] Copy descriptors on prototype map transition.

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : v8.mobile_infinite_scroll_tbmv2
  Metric       : v8-gc-total_max/discourse
  Change       : 31.74% | 15.7685 -> 20.7726666667

Revision                           Result                  N
chromium@481581                    15.7685 +- 2.77483      6      good
chromium@481584                    17.0567 +- 1.97234      6      good
chromium@481586                    15.9003 +- 3.28109      6      good
chromium@481586,v8@6681949808      16.1503 +- 2.33775      6      good
chromium@481586,v8@79ec067252      16.4923 +- 4.51655      6      good
chromium@481586,v8@5d8840e24e      20.6422 +- 2.32023      6      bad       <--
chromium@481587                    21.0088 +- 3.18797      6      bad
chromium@481592                    20.7727 +- 1.90812      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=discourse v8.mobile_infinite_scroll_tbmv2

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970644222465204768


For feedback, file a bug with component Speed>Bisection

The CL was reverted.