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

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


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

android-nexus5x-perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/104ce34fe40000

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

Perfetto: Fix for worker threads not finalizing proto packets by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/d420ce980291dbdee3d8a68594afbbfe5b75fbb4
tasks_per_frame_total_all: 19.72 → 26.97 (+7.251)

media/gpu/test: Move TextureRef class out of video_decode_accelerator_unittest_helpers. by dstaessens@chromium.org
https://chromium.googlesource.com/chromium/src/+/72cea2dc662c5982e23c5e8f65abb448ede67d6f
tasks_per_frame_total_all: 26.97 → 27.17 (+0.1956)

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.