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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-latency-mark-compactor_avg/browse_media/browse_media_pinterest

Revision             Result                  N
chromium@439564      20.7257 +- 29.3131      21      good
chromium@439798      28.5671 +- 55.4873      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.pinterest v8.browsing_desktop

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

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


| 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 Tests>AutoBisect.  Thank you!

Nothing is going to happen here anymore and it actually recovered.