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

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


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

android-nexus6

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

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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-incremental-start_sum/browse_news/browse_news_washingtonpost

Revision             Result                  N
chromium@492247      4.05376 +- 1.22605      21      good
chromium@492249      3.99143 +- 2.56121      21      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.runtimestats.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Jakob Kummerow
  Commit : 05e862f78398d8bbeacc7f9e19bbb41c408e709b
  Date   : Fri Aug 04 01:27:42 2017
  Subject: Cache StoreIC-Transition handlers

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-incremental-start_sum/browse_news/browse_news_washingtonpost
  Change       : 53.90% | 2.63066666667 -> 4.04866666667

Revision                           Result                   N
chromium@492049                    2.63067 +- 0.821549      6      good
chromium@492129                    2.66917 +- 0.407758      6      good
chromium@492149                    2.57617 +- 1.08679       6      good
chromium@492159                    2.644 +- 0.354691        6      good
chromium@492161                    2.4225 +- 1.09817        6      good
chromium@492161,v8@5614747680      2.51517 +- 0.766905      6      good
chromium@492161,v8@2fd5e70a03      2.421 +- 1.00866         6      good
chromium@492161,v8@9735d7f109      2.45467 +- 0.755727      6      good
chromium@492161,v8@0caf1d2029      2.806 +- 0.557604        6      good
chromium@492161,v8@05e862f783      4.2665 +- 0.59452        6      bad       <--
chromium@492162                    4.1555 +- 0.432501       6      bad
chromium@492164                    3.64633 +- 0.936881      6      bad
chromium@492169                    3.96067 +- 0.727019      6      bad
chromium@492209                    3.81583 +- 1.00305       6      bad
chromium@492368                    4.04867 +- 0.348826      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.runtimestats.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection