Caused by CLs in: https://chromium.googlesource.com/chromium/src/+log/8d204a47e52eba9b79de87c8df23c3c3c0d70327..78dd26a211196944f095a20fefcd3ed2dafebe6d

Link to size graph: https://chromeperf.appspot.com/report?sid=bb23072657e2d7ca892a1c3fa4643b1ee29b3a0a44d0732adda87168e89c0380&num_points=10&rev=559957

Debugging size regressions is documented at: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/apk_size_regressions.md#Debugging-Apk-Size-Increase

Based on the graph: 1052kb of native code, 13kb of dex, 48kb of compressed android resources, 11kb native stored resources l10n, 3kb non compiled android resources size.

We should probably bisect this just like  issue 852523 

It typically takes about a week of engineering time to reduce binary size by 100kb so we'd really appreciate you taking some time exploring options to address this regression!

@Chris - any tips on how I can get started bisecting? Not sure if you were doing it locally or not.