New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 793991 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
thomasanderson@chromium.org
█ timbrown@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chrome Linux 64.0.3282.x install package grow by 2.7 MB

Project Member Reported by thestig@chromium.org, Dec 11 2017 
Comparing google-chrome-stable_64.0.3282.14-1_amd64.deb vs google-chrome-stable_63.0.3239.90-1_amd64.deb, the file size has grown to 49.42 MB from 46.76. We should figure out why it happened and decide if it's ok.

BTW, if we have a Linux bug triage rotation, we should add checking the release branch installer size to the TODO list. The process will get easier if someone fixes bug 749764.

Comment 1 by thomasanderson@chromium.org, Dec 12 2017 

timbrown@ if interested the list of releases is at go/XMaeAvRaLZXE8cagZhZwVJirv44dScaQ
You can see the sizes in the UI and do a sort of bisect on the versions to find out when the size increased

Comment 2 by thestig@chromium.org, Dec 19 2017 

BTW, I shared a very unexciting internal spreadsheet with sizes for releases. I've been working on updating it to figure out why this happened.

Comment 3 by thestig@chromium.org, Dec 20 2017

Status: WontFix (was: Untriaged)
I don't see anything actionable here.

This is due to  bug 781272  and  bug 785567 , along with lots of new code creeping in. The chrome binary's on disk size grew by ~4 MB, but that's offset by smaller resources.pak / swiftshader / nacl_helper. So the overall on-disk install size only went up by 1 MB. Because the ~2 MB reduction in resources.pak is from compression, the .deb does not get that benefit.

Comment 4 by timbrown@chromium.org, Dec 23 2017 

Thanks for looking into that.
►

Sign in to add a comment