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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA3_b1sgoM


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

chromium-rel-win10

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@378430         102133.9456225318.765939 18          good
chromium@378451         104673.2114147302.769928 18          bad

Bisect job ran on: winx64_10_perf_bisect
Bug ID: 597236

Test Command: python src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --also-run-disabled-tests memory.long_running_idle_gmail_background
Test Metric: V8_MemoryHeapSampleTotalCommitted/https___mail.google.com_mail_
Relative Change: 4.98%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/475
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9017404043114639168


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with label Cr-Tests-AutoBisect.  Thank you!

AFAICT, all the alerts have recovered so you can probably close this bug.