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

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


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

chromium-rel-win10

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

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


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@413382  18161547  141092   5  good
chromium@413390  18130210  108458   5  good
chromium@413391  18863390  87647.9  5  bad
chromium@413392  18777644  183333   5  bad
chromium@413394  18823356  137198   5  bad
chromium@413398  18828325  83286.3  5  bad

Bisect job ran on: winx64_10_perf_bisect
Bug ID: 641891

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:old_space:allocated_objects_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:old_space:allocated_objects_size_avg
Relative Change: 3.67%
Score: 0

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


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6380768505364480

| 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 component Tests>AutoBisect.  Thank you!

Didn't see that we basically went back to normal after a revert that causes and improvement.