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

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


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

win-zenbook

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@413381  1422460  7496.26  5  good
chromium@413388  1425229  6961.83  5  good
chromium@413390  1419669  4727.38  5  good
chromium@413391  1469679  5637.25  5  bad
chromium@413394  1468977  3823.02  5  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 641889

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:map_space:allocated_objects_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:map_space:allocated_objects_size_avg
Relative Change: 3.27%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/457
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9003005555356357808


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

| 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.