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

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


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

chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-x64-dual

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

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

Suspected Commit
  Author : Zhenyao Mo
  Commit : 39d8a7f229e1330e72724895eb4730b7108e47a0
  Date   : Mon Oct 30 13:45:42 2017
  Subject: Revert "One step further into moving GPU feature decisions to GPU process"

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/browse_social/browse_social_twitter
  Change       : 6.83% | 46854067.927 -> 50054176.5524

Revision             Result                   N
chromium@512468      46854068 +- 8680633      14      good
chromium@512478      47002683 +- 4470591      9       good
chromium@512483      45737153 +- 7061118      14      good
chromium@512484      45941500 +- 9021867      14      good
chromium@512485      48752201 +- 4176269      14      bad       <--
chromium@512486      49196338 +- 6064486      14      bad
chromium@512488      49358422 +- 7958184      21      bad
chromium@512507      50054177 +- 9001071      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.twitter v8.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection