Tracking down large fuchsia binary size increase

15 views
Skip to first unread message

Andrew Brown

unread,
Apr 29, 2026, 12:04:11 AMApr 29
to binary-size
Hi all,

I'm trying to track down an unexpectedly large binary size increase in Fuchsia on https://chromium-review.googlesource.com/c/chromium/src/+/5273743.

Compressed growth when submitting the CL was 49,152b and uncompressed 20,496b.

I compiled for fuchsia locally, with and without the change, to try and track things down. The binary_sizes.py script reports that my change actually *decreases* in size by 12,272b uncompressed and 8,192b compressed.

I installed and ran Bloaty; the VM size decreased by 10.8kB. The file size increased by 208kB, but those changes are made up of near a hundred thousand tiny, irrelevant changes: stuff like +30b in `blink::CSSParserFastPaths::ParseColor()` or +516b in `gen/v8/src/inspector/protocol/Debugger.cpp`. As best I can tell from Bloaty output, I would expect there to be a small, 1-2kB increase in uncompressed file size. I don't know where 20kB reported on the CL could be coming from.

Any advice would be greatly appreciated! Thanks :)
Reply all
Reply to author
Forward
0 new messages