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

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


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

chromium-rel-mac-retina

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

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

Suspected Commit
  Author : chrome-cron
  Commit : 85eb0199323407db76feaa192e0d0a0fd9b24f6f
  Date   : Sat Mar 11 04:02:40 2017
  Subject: Updating trunk VERSION from 3038.0 to 3039.0

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-incremental-step_sum/browse_news/browse_news_cnn
  Change       : 150.84% | 273.351571429 -> 685.665333333

Revision             Result                  N
chromium@456261      273.352 +- 250.002      14      good
chromium@456273      267.917 +- 214.638      14      good
chromium@456274      600.599 +- 136.562      3       bad       <--
chromium@456277      515.427 +- 136.622      3       bad
chromium@456279      685.246 +- 164.596      4       bad
chromium@456285      583.905 +- 9.34287      3       bad
chromium@456308      601.935 +- 177.367      3       bad
chromium@456354      685.665 +- 166.77       3       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=browse.news.cnn v8.browsing_desktop

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

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


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