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

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


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

chromium-rel-mac11-pro

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

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

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop_classic
  Metric       : v8-gc-latency-mark-compactor_max/browse_media/browse_media_youtube

Revision             Result                  N
chromium@458128      4.31448 +- 3.70337      21      good
chromium@458282      4.43967 +- 4.79805      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.media.youtube v8.runtimestats.browsing_desktop_classic

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

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


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

Only shows up on old pipeline (--no-turbo) graphs, closing.