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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=c6ddd50aa92aac708b7fad215e48aa1946c242c3b48f859705cc9940a27aaf57


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

android-webview-nexus5X

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

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

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-total_sum/browse_social/browse_social_tumblr_infinite_scroll

Revision             Result                  N
chromium@485850      1879.08 +- 438.355      21      good
chromium@485963      1857.46 +- 325.281      21      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=browse.social.tumblr.infinite.scroll v8.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection

=== 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 : 5e724050da616ff88715304b72809edd59e0c036
  Date   : Wed Jul 12 12:01:42 2017
  Subject: [heap] Replace marking deque with marking worklist.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-incremental-step_sum/browse_tech/browse_tech_discourse_infinite_scroll
  Change       : 6.32% | 148.160666667 -> 157.522

Revision                           Result                  N
chromium@485905                    148.161 +- 3.16618      6      good
chromium@485960                    149.789 +- 6.11402      6      good
chromium@485967                    150.249 +- 4.15351      6      good
chromium@485969                    148.024 +- 4.15083      6      good
chromium@485970                    148.112 +- 6.23823      9      good
chromium@485970,v8@0d910860c9      167.477 +- 147.351      9      good
chromium@485970,v8@97f5e1fad0      151.419 +- 3.2323       6      good
chromium@485970,v8@5e724050da      160.979 +- 6.17778      9      bad       <--
chromium@485971                    159.87 +- 3.99842       9      bad
chromium@485974                    159.905 +- 1.73953      6      bad
chromium@485988                    186.971 +- 154.103      6      bad
chromium@486015                    157.522 +- 5.0778       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.tech.discourse.infinite.scroll v8.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection

The 50% regression has recovered. Other regressions are small compared to the noise leve.