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

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


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

Win 7 Nvidia GPU Perf

media.desktop - Benchmark documentation link:
  None

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/11f3ad8fe40000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/11f3ad8fe40000

All of the runs failed. The most common error (20/20 runs) was:
SwarmingTestError: The test failed. No Python exception was found in the log.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16ddad94140000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/16ddad94140000

All of the runs failed. The most common error (20/20 runs) was:
SwarmingTestError: The test failed. No Python exception was found in the log.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12f38c32140000

^^ re-running now that blocking bugs are fixed

📍 Found significant differences after each of 8 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/12f38c32140000

Adding UseCounter on document freeze. by kdillon@chromium.org
https://chromium.googlesource.com/chromium/src/+/bbacb1fc64b4ffc4b92723a0fa891b630b678837
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 1.014e+07 → 1.022e+07 (+7.554e+04)

Use SharedImageInterface for one-copy staging buffers by piman@chromium.org
https://chromium.googlesource.com/chromium/src/+/9058f7866e74b92eeef1c30780522fba0740d2f3
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 1.021e+07 → 1.096e+07 (+7.508e+05)

[TaskScheduler]: Migrate off of ScopedAllowWait in /android_webview by etiennep@chromium.org
https://chromium.googlesource.com/chromium/src/+/bcc4146d6611e4979f5bc1f71274d17a4f2e1a1e
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 1.095e+07 → 1.084e+07 (-1.065e+05)

Roll src/third_party/skia 60b6bc3c2950..f47abb48757f (2 commits) by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/51354d4206a9930be5070ee9b56f6ca5f61d03ad
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 1.086e+07 → 1.097e+07 (+1.105e+05)

Revert "Reland "Perfetto: Optimization to avoid string table lookup for _END events"" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/a6bcdc64c6eec541ccc82f67a166f6854b6180cf
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 1.097e+07 → 1.086e+07 (-1.179e+05)

Create duplicate src-side configs for all chromium.lkgr bots. by bpastene@chromium.org
https://chromium.googlesource.com/chromium/src/+/7d61bb26afe6b8e0749af5de3d28513eca6c9c19
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 1.086e+07 → 1.093e+07 (+6.971e+04)

[service-manager] Clean up Connector API by rockot@google.com
https://chromium.googlesource.com/chromium/src/+/a86fa542fff877da2589b284d800b3924d30710f
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 1.098e+07 → 1.07e+07 (-2.801e+05)

[Media Engagement] Remove histogram by beccahughes@chromium.org
https://chromium.googlesource.com/chromium/src/+/a78d20743acc9e2777aa375d4dee2d8e970317bc
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 1.07e+07 → 1.093e+07 (+2.259e+05)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  None

Removing myself as my CL would not cause any performance impact. Assigning to piman@ as their change is graphics related.