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

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


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

android-nexus7v2

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

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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : v8-gc-latency-mark-compactor_sum/browse_media/browse_media_youtube

Revision             Result                 N
chromium@460691      54.1047 +- 47.028      21      good
chromium@460947      53.3463 +- 35.222      21      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.media.youtube v8.runtimestats.browsing_mobile_classic

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

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


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

The graph recovered.