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

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


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

win-32

updowndota: This is due to "Add strings for voice interaction OOBE error screen" (https://chromium-review.googlesource.com/591635)

This CL only add a few string constants which are not even used right now. How possible will this cause such regressions?

+hans@

I think the alert and the graph is probably off by one, so the culprit would be crrev.com/490494, which looks very likely to cause such a large jump in binary size.

Hans, what do you think?

Yes, this matches the expected size changes from the clang switch. 32-bit sizes increase and 64-bit sizes decrease.