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

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


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

chromium-rel-mac11-pro

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

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

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : memory.long_running_idle_gmail_background_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/https___mail.google.com_mail_

Revision             Result                     N
chromium@475510      94114905 +- 33363718       21      good
chromium@475610      100048131 +- 24571235      21      bad

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=https...mail.google.com.mail. memory.long_running_idle_gmail_background_tbmv2

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

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


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

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

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

Suspected Commit
  Author : altimin
  Commit : f39f12be44e4d35eb25c7a58b1895c751da723f5
  Date   : Tue May 30 17:53:12 2017
  Subject: [scheduler] Add general task queue to fix touch latency regression.

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : memory.long_running_idle_gmail_background_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/https___mail.google.com_mail_
  Change       : 6.11% | 93379716.5714 -> 99081692.0

Revision             Result                     N
chromium@475510      93379717 +- 26976345       21      good
chromium@475561      90427731 +- 24042221       14      good
chromium@475585      90454563 +- 15744153       14      good
chromium@475589      94587997 +- 31011958       21      good
chromium@475590      97857303 +- 11128815       6       good
chromium@475591      102849072 +- 762122        6       bad       <--
chromium@475592      100468384 +- 15266726      14      bad
chromium@475598      99396916 +- 14539239       9       bad
chromium@475610      99081692 +- 20725824       14      bad

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=https...mail.google.com.mail. memory.long_running_idle_gmail_background_tbmv2

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

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


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