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

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


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

Android Nexus5 Perf
android-nexus5x-perf

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

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

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

Turn on full masking with untrusted-code-mitigations by jarin@chromium.org
https://chromium.googlesource.com/v8/v8/+/6a6f050e18b90d5b498d85455e598ca68b14238f
0.2548 → 0.9966 (+0.7418)

Revert "Reland "Enable Perfetto by default for all telemetry tests"" by pasko@chromium.org
https://chromium.googlesource.com/chromium/src/+/f36de8b1bdc40bf31455b052ef63338072b093da
0.9311 → 0.4646 (-0.4665)

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

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

Pinpoint found an effect from Perfetto revert, which is probably legitimate (even though small). The (bigger) regression here is at:

Turn on full masking with untrusted-code-mitigations by jarin@chromium.org
https://chromium.googlesource.com/v8/v8/+/6a6f050e18b90d5b498d85455e598ca68b14238f

looking at the patch .. the regression is probably expected, reassigning to check that the magnitude is also within expected bounds