With no significal changes in ldd output, chromium-94.x have 30% bigger binary and refresh screen slower. It is not normal for evolution. www-client/chromium-93.0.4577.51: 40 files, 34 non-files, 347.1M -rwxr-xr-x 1 root root 268M 08-20 06:39 /usr/lib64/chromium-browser/chrome www-client/chromium-94.0.4606.20: 42 files, 33 non-files, 467.1M -rwxr-xr-x 1 root root 348M 08-28 00:14 /usr/lib64/chromium-browser/chrome I've not changed USE, compilers...
I guess you build with USE=-official. That enables DCHECK by default, which of course increases binary size. Either we switch to IUSE=+official or add a new USE flag for controlling DCHECK.
(In reply to Stephan Hartmann from comment #1) > I guess you build with USE=-official. [...] You are right! :-) USE=cups custom-cflags hangouts proprietary-codecs pulseaudio suid system-icu vaapi wayland widevine -js-type-check -kerberos -official -screencast If +official won't remove important/popular features, I vote for not adding flags, but set +official by default :-)
Same problem here, sluggish chromium response, mouse wheels scroll speed change (very slow) and unsure about the binary size, on amd64 arch mine is currently: 343MB. What are the major changes apart from this DCHECK function between +official and the current default -official?
The name "official build" is a bit confusing. In the end it is a release build and enables some more optimizations which improve speed and size. On the other hand it makes debugging harder, because e.g. unwind tables are removed. With next bump I plan to add USE=debug to control DCHECK functionality.
There must be something else - with +official chromium-94 is still much bigger: www-client/chromium-94.0.4606.20: 42 files, 33 non-files, 441.9M -rwxr-xr-x 1 root root 344M 09-02 07:48 /usr/lib64/chromium-browser/chrome
# equery s chromium -official * www-client/chromium-92.0.4515.159 Total files : 73 Total size : 340.32 MiB # equery s chromium +official * www-client/chromium-93.0.4577.58 Total files : 73 Total size : 299.37 MiB
Shaved off about 40 minutes off of build time too. Why did I not know about it before?
(In reply to Michael from comment #6) You are comparing v92 and v93, and all the problem surfaced with v94.
for me rebuilding with +official brought down the binary to 231MB: $ ls -alhrt /usr/lib64/chromium-browser/chrome -rwxr-xr-x 1 root root 231M Sep 2 12:33 /usr/lib64/chromium-browser/chrome Seems like this also caused performance increase... so unsure why the developer build is the 'default' ?
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a06987c846f20b252b846da05a4131f85dce9cd6 commit a06987c846f20b252b846da05a4131f85dce9cd6 Author: Stephan Hartmann <sultan@gentoo.org> AuthorDate: 2021-09-03 06:36:54 +0000 Commit: Stephan Hartmann <sultan@gentoo.org> CommitDate: 2021-09-03 06:37:42 +0000 www-client/chromium: beta channel bump to 94.0.4606.31 Add USE=debug to control DCHECK feature. Bug: https://bugs.gentoo.org/811138 Bug: https://bugs.gentoo.org/807881 Package-Manager: Portage-3.0.20, Repoman-3.0.3 Signed-off-by: Stephan Hartmann <sultan@gentoo.org> www-client/chromium/Manifest | 2 +- ...romium-94.0.4606.20.ebuild => chromium-94.0.4606.31.ebuild} | 10 ++++++---- www-client/chromium/metadata.xml | 1 + 3 files changed, 8 insertions(+), 5 deletions(-)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=76d1579fc29959d24ac2f1d7cc6a8f65b01f1743 commit 76d1579fc29959d24ac2f1d7cc6a8f65b01f1743 Author: Stephan Hartmann <sultan@gentoo.org> AuthorDate: 2021-09-04 07:48:19 +0000 Commit: Stephan Hartmann <sultan@gentoo.org> CommitDate: 2021-09-04 07:48:35 +0000 www-client/chromium: dev channel bump to 95.0.4628.3 Closes: https://bugs.gentoo.org/811138 Closes: https://bugs.gentoo.org/807881 Package-Manager: Portage-3.0.20, Repoman-3.0.3 Signed-off-by: Stephan Hartmann <sultan@gentoo.org> www-client/chromium/Manifest | 4 ++-- ...romium-95.0.4621.4.ebuild => chromium-95.0.4628.3.ebuild} | 12 ++++++------ 2 files changed, 8 insertions(+), 8 deletions(-)
Is there some other catch with the official/release build vs developer build? Like not being able to install extentions from a file?
