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

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


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

chromium-rel-mac11
chromium-rel-win7-x64-dual

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

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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/long_running_tools/long_running_tools_gmail-foreground

Revision             Result                     N
chromium@512108      117455133 +- 41840277      21      good
chromium@512157      115006697 +- 55266137      20      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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=long.running.tools.gmail.foreground system_health.memory_desktop

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

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


For feedback, file a bug with component Speed>Bisection

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 9624ee2a5b59e1a5a6053e95ec98a01f76cf92d3
  bad_revision : ea3bcc536b3aa5c0f953524bf83c2ac3987fd2e4

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/long_running_tools/long_running_tools_gmail-foreground

Revision             Result                     N
chromium@511500      108394311 +- 46479934      21       good
chromium@511876      112736317 +- 38416847      21       good
chromium@512064      ---                        ---      build failure
chromium@512065      120522563 +- 28720635      14       bad
chromium@512250      121810806 +- 28847252      14       bad
chromium@513000      118265292 +- 53381369      20       bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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=long.running.tools.gmail.foreground system_health.memory_desktop

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

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


For feedback, file a bug with component Speed>Bisection