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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg4sOGvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgkqj4qwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg4oOjuwkM


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

chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual

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

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

===== 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     Std Dev  N   Good?
chromium@402769  5749893  95677.9  12  good
chromium@402780  5764037  28219.8  18  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 628182

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests top_10_mobile_memory_ignition
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max/http___www.baidu.com_s?word_google
Relative Change: 0.23%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1715
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007164873305348512


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

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

allocated_object_size_max depends on when the last gc happened. So, this variation could be cause by the change in timing of gc. There is no regression in the allocated_object_size_avg which gives a better approximation of the heap size. So marking this bug as won't fix.