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

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


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

Android Nexus5X WebView Perf
Android Nexus6 WebView Perf
mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/10573723e40000

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/10573723e40000

Perfetto: Fix for worker threads not finalizing proto packets by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/d420ce980291dbdee3d8a68594afbbfe5b75fbb4
thread_raster_cpu_time_per_frame: 0 → 0.3454 (+0.3454)

media/gpu/test: Move TextureRef class out of video_decode_accelerator_unittest_helpers. by dstaessens@chromium.org
https://chromium.googlesource.com/chromium/src/+/72cea2dc662c5982e23c5e8f65abb448ede67d6f
thread_raster_cpu_time_per_frame: 0.3454 → 0.3152 (-0.0302)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Changes to TextureRef would definitely not affect performance, as it only moves some test-related code to a separate file, nothing is added/changed.