I've noticed that apt
estimates the upgrade to take 48.1MB more space on upgrading from 62.0.3202.94-0ubuntu0.16.04.1317
to 63.0.3239.84-0ubuntu0.16.04.1
. I've skimmed through apt changelog chromium-browser
and don't see anything that's described as taking much more space. Is there a quick way to see what files changed with apt
or anyone who knows or will find the reason?
$ apt list --upgradable
chromium-browser/xenial-updates,xenial-security 63.0.3239.84-0ubuntu0.16.04.1 amd64 [upgradable from: 62.0.3202.94-0ubuntu0.16.04.1317]
chromium-codecs-ffmpeg-extra/xenial-updates,xenial-security 63.0.3239.84-0ubuntu0.16.04.1 amd64 [upgradable from: 62.0.3202.94-0ubuntu0.16.04.1317]
$ sudo apt dist-upgrade
The following packages will be upgraded:
chromium-browser chromium-codecs-ffmpeg-extra
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 74.4 MB of archives.
After this operation, 48.1 MB of additional disk space will be used.
The size difference seems to be from a new
v8_context_snapshot_generator
binary file. I extracted the contents of the debs and compared them:This seems to be a new tool meant to speed creation of V8 contexts. V8 is the JavaScript engine used by Chromium, and creating new V8 contexts is a significant part of the time taken for loading a webpage. The design document suggests that creating contexts from V8 context snapshots should lead to a speedup of up to 3x, and this is meant to be a helper program for creating snapshots in the first place.
However, reading the design doc suggests including the tool in the package might be an accident, and hence a packaging bug:
And:
The implication is that
v8_context_snapshot_generator
is to be run during package build time, and not on individual user systems. And the relative small size predicted increase for Android suggests that it doesn't include a 44 MB tool.