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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtP3HpgoM


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

Google Chrome Linux x64

The only change in log that could possibly have affected sizes is:
https://chromium.googlesource.com/chromium/src/+/ab6f6ae93d12cf5913efbb7f1f1f6c34e2cab39b, but it seems extremely unlikely.

Marking WontFix, but assigning to amistry to double check.

Am I reading that right? Chrome is 2.8GB? Doesn't sound right. And if this is chrome+debugging symbols, is this even a meaningful alert?

Mojo does generate code and do a lot of template instantiations. A release build will inline or fold a lot of it, resulting in a tiny, but known increase in binary size in a release build.

+sullivan@

Do the sizes tests have an owner?

There's no owner listed in the test owners doc.

+rpop

We could really use some help finding an owner for sizes for linux! See  bug 608067 .