Issue metadata
Sign in to add a comment
|
Autofill binary size growth is significant for M69->M72 (320kb) |
||||||||||||||||||||
Issue descriptionHere's a sizes diff showing where the growth came from: https://storage.googleapis.com/chrome-supersize/viewer.html?load_url=milestones%2Farm%2FMonochrome.apk%2Freport_69.0.3497.91_72.0.3626.7.ndjson&group_by=component&include=autofill&exclude=assets%2Funwind_cfi&diff_mode=on For an increase of this size, we're generally looking for: * Ways to significantly reduce, and/or * Justification as to why the size hit is necessary & "worth it". There are some tips here: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/apk_size_regressions.md#step-2_analyze But generally these investigations require specific deep-dives & some trial and error. Using the android-binary-size trybot, or locally running //tools/binary_size/diagnose_bloat.py can also help. binary-size@chromium.org is also a list that exists for help with such things.
,
Dec 18
Roger posted a breakdown of this in our team chat back on Dec. 10th; it was mostly autofill_assistant, along with ongoing feature work (StrikeDatabase/LegacyStrikeDatabase) and a couple of related protos.
,
Dec 18
Is this feature launched? If not, is it behind a GN arg so that we could disable it for beta & stable (we did this for feed, and are currently doing it for vulkan support)
,
Jan 9
Autofill Assistant is launching in M72. And we are considering to convert it to dynamic module.
,
Jan 18
(4 days ago)
,
Jan 18
(4 days ago)
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ma...@chromium.org
, Dec 10Components: UI>Browser>Autofill
Owner: ----