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

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


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

android-nexus7v2
chromium-rel-mac-retina
chromium-rel-mac11-pro

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-phantom-handle-callback_max/browse_news/browse_news_cricbuzz

Revision             Result                   N
chromium@497870      0.264333 +- 0.15272      6      good
chromium@497977      2.41617 +- 1.79346       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.cricbuzz v8.runtimestats.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection