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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=1362f700dc7dc292e17ce235042291adf5a134356c4192ac8b1168aac04bddaa


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

chromium-rel-mac11

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

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

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-total_max/browse_news/browse_news_flipboard

Revision             Result                  N
chromium@490144      18.3083 +- 13.8272      21      good
chromium@490311      18.1511 +- 13.0434      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=browse.news.flipboard v8.runtimestats.browsing_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8972178003726827632


For feedback, file a bug with component Speed>Bisection

Not reproducible.