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

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


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

chromium-rel-win7-dual

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

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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : memory.long_running_idle_gmail_background_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_max/memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_max

Revision             Result                    N
chromium@500247      73882088 +- 38140782      21      good
chromium@500286      75828078 +- 35161626      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.long_running_idle_gmail_background_tbmv2

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

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


For feedback, file a bug with component Speed>Bisection