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

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


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

chromium-rel-mac11-pro
chromium-rel-win7-gpu-nvidia

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

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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : oortonline_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/http___oortonline.gl__run

Revision             Result                     N
chromium@502894      374839003 +- 24150197      21      good
chromium@502979      371318784 +- 52470726      21      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=http...oortonline.gl..run oortonline_tbmv2

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

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


For feedback, file a bug with component Speed>Bisection