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

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


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

chromium-rel-mac11-pro

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

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

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

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : memory.long_running_idle_gmail_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_os:system_memory:private_dirty_size_avg/memory:chrome:renderer_processes:reported_by_os:system_memory:private_dirty_size_avg

Revision             Result                      N
chromium@469251      435132511 +- 99783991       21      good
chromium@469293      421112862 +- 128407719      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 memory.long_running_idle_gmail_tbmv2

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

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


| 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/8980129937778349168

=== Auto-CCing suspected CL author karandeepb@chromium.org ===

Hi karandeepb@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : karandeepb
  Commit : 77b81a68158815ad8b45bc66fd424f430cbf7da5
  Date   : Thu May 04 05:21:03 2017
  Subject: [Blink-scheduler] Correct description for [Background/Foreground]RendererMainThreadLoad histograms.

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : memory.long_running_idle_gmail_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_os:system_memory:private_dirty_size_avg/memory:chrome:renderer_processes:reported_by_os:system_memory:private_dirty_size_avg
  Change       : 7.86% | 442796720.128 -> 407984764.659

Revision             Result                      N
chromium@469251      442796720 +- 21173818       21      good
chromium@469272      444519385 +- 16033019       21      good
chromium@469273      405702378 +- 57274097       6       bad       <--
chromium@469274      397198996 +- 53483034       6       bad
chromium@469275      400062815 +- 46707956       6       bad
chromium@469278      406287227 +- 80379082       9       bad
chromium@469283      398632097 +- 50166450       6       bad
chromium@469293      407984765 +- 101566523      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 memory.long_running_idle_gmail_tbmv2

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

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


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

My CL just changed a histogram description. Un-assigning myself.

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

Suspected Commit
  Author : karandeepb
  Commit : 77b81a68158815ad8b45bc66fd424f430cbf7da5
  Date   : Thu May 04 05:21:03 2017
  Subject: [Blink-scheduler] Correct description for [Background/Foreground]RendererMainThreadLoad histograms.

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : memory.long_running_idle_gmail_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_os:system_memory:private_dirty_size_avg/memory:chrome:renderer_processes:reported_by_os:system_memory:private_dirty_size_avg
  Change       : 9.68% | 443024475.333 -> 401319038.608

Revision             Result                      N
chromium@469251      443024475 +- 2395452        6       good
chromium@469272      443290083 +- 11367526       14      good
chromium@469273      397902052 +- 51024238       6       bad       <--
chromium@469274      419158055 +- 40259277       9       bad
chromium@469275      398960395 +- 82395547       14      bad
chromium@469278      422942874 +- 42028411       14      bad
chromium@469283      413406561 +- 123131322      21      bad
chromium@469293      401319039 +- 81539797       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 memory.long_running_idle_gmail_tbmv2

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

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


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

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.