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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Yutaka Hirano
  Commit : 84047549ac37bab70d7306566c912e59131f3e1f
  Date   : Mon Jun 19 04:16:15 2017
  Subject: [Loading] Save one post-task when the data pipe is ready on arrival

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_tools/load_tools_weather
  Change       : 75.03% | 38084935.1111 -> 66591030.6667

Revision             Result                    N
chromium@480339      38084935 +- 422903        9      good
chromium@480341      38023949 +- 441841        9      good
chromium@480342      63177295 +- 27038922      9      bad       <--
chromium@480345      66165511 +- 1210198       6      bad
chromium@480350      63207185 +- 27039256      9      bad
chromium@480360      65638183 +- 1669211       6      bad
chromium@480380      66591031 +- 1846777       6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.weather system_health.memory_desktop

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

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


| 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 Speed>Bisection.  Thank you!