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

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


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

chromium-rel-win7-gpu-nvidia

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

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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max

Revision             Result                     N
chromium@445299      115500416 +- 23086926      8      good
chromium@445301      112294366 +- 15223518      8      bad

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

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8989403716294927600

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6064252600713216


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

Max memory seems to be flaky. It is very time sensitive.

 Issue 685601  has been merged into this issue.