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

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


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

chromium-rel-win7-x64-dual

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

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

Hi hajimehoshi@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 : Hajime Hoshi
  Commit : 7679db6eae7ce7ce4614f0980dad28df4ba0df27
  Date   : Mon Jul 31 09:01:50 2017
  Subject: Use resident bytes for tracking SharedMemory usage

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : V8 C++:duration_avg/browse_tech/browse_tech_discourse_infinite_scroll
  Change       : 4.16% | 2702.03635714 -> 2816.12788889

Revision             Result                  N
chromium@490714      2702.04 +- 129.197      14      good
chromium@490725      2710.52 +- 129.331      14      good
chromium@490729      2723.76 +- 203.604      14      good
chromium@490731      2716.71 +- 161.062      21      good
chromium@490732      2757.85 +- 142.067      14      bad       <--
chromium@490750      2816.13 +- 173.078      9       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.tech.discourse.infinite.scroll v8.runtimestats.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection