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

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


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/1196caf7e40000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1196caf7e40000

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: 45.39 → 59.4 (+14.02)

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

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

Mainly graphs recovering to pre-Perfetto levels; some are due to extra PostTasking by Perfetto for returning full chunks to the service.

 Issue 904432  has been merged into this issue.

 Issue 903169  has been merged into this issue.

 Issue 903154  has been merged into this issue.

 Issue 902846  has been merged into this issue.

 Issue 902734  has been merged into this issue.

Issue 902458 has been merged into this issue.

 Issue 902454  has been merged into this issue.

 Issue 903152  has been merged into this issue.

 Issue 903151  has been merged into this issue.

 Issue 902753  has been merged into this issue.

 Issue 901889  has been merged into this issue.

 Issue 903134  has been merged into this issue.