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

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


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

linux

Assigning to sheriff gbiv@chromium.org because this autoroll is the only CL in range:
Roll AFDO from 69.0.3444.0_rc-r1 to 69.0.3446.0_rc-r1

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file a bug against
gbiv@chromium.org. Additional context:  https://crbug.com/805539 

The AutoRoll server is located here: https://afdo-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=gbiv@chromium.org

Change-Id: Ic1f4df5dd1b4ddaa06d0e00ef088e85fa6d8d3e3
Reviewed-on: https://chromium-review.googlesource.com/1080451
Reviewed-by: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#563170}

 Issue 848273  has been merged into this issue.

Android filed an issue about this size bump, too. I'd say that's rare, but I said that size swings were rare yesterday about one from a few days ago, and now we have an even larger one today. :)

Fingers crossed that the next roll or two fixes it, and I'll include this in my "figure out why AFDO is too noisy" investigations. Thanks!