GNU bug report logs - #35243
ungoogled-chromium build stops and freezes the system

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 35243 in the body.
You can then email your comments to 35243 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: znavko <at> disroot.org
To: "bug-guix" <bug-guix <at> gnu.org>
Subject: ungoogled-chromium build stops and freezes the system
Date: Fri, 12 Apr 2019 10:15:50 +0000

[Message part 1 (text/plain, inline)]

My bug report is this https://github.com/Eloston/ungoogled-chromium/issues/730

During update with `guix pull && guix package -u` ungoogled-chromium build process stops on build derivation on 84% three times in a row.

$ guix describe
Generation 94 Apr 11 2019 21:13:38 (current)
 guix a6de569
 repository URL: https://git.savannah.gnu.org/git/guix.git
 branch: master
 commit: a6de569ea224a2f482c4d13c5f62240d1b1543a0

$ chromium --version
Chromium 73.0.3683.86

It shows this error message http://0x0.st/zNo0.jpg
"A script on this page may be busy, or it have stopped responding...
Script:chrome://global/content/bindings/popup.xml:276"

[Message part 2 (text/html, inline)]

Message #8 received at 35243 <at> debbugs.gnu.org (full text, mbox):

From: znavko <at> disroot.org
To: 35243 <at> debbugs.gnu.org
Subject: Re: bug#35243: ungoogled-chromium build stops and freezes the system
Date: Fri, 12 Apr 2019 18:14:38 +0000

[Message part 1 (text/plain, inline)]

Today I've made `guix system reconfigure /etc/config.scm` with icecat and ungoogled-chromium in (operating-system (packages (list ...))) variable and have caught an error:

# guix system reconfigure /etc/config.scm
...
kPtr<net::BidirectionalStreamQuicImpl>, net::BidirectionalStreamImpl::Delegate*, int>; long unsigned int ...indices = {0, 1, 2}]’:
 83% [############################################################ ]??@ build-log 3235 86
??mojo_base::mojom::internal::BigBuffer_Data’ is less than 8 [-Wpacked-not-aligned]
 86% [############################################################### ]builder for `/gnu/store/1kfhs4njz2dvpry3dqkkj8v62kc49xy6-ungoogled-chromium-73.0.3683.103-0.4c7fb6d.drv' failed with exit code 1
build of /gnu/store/1kfhs4njz2dvpry3dqkkj8v62kc49xy6-ungoogled-chromium-73.0.3683.103-0.4c7fb6d.drv failed
View build log at '/var/log/guix/drvs/1k/fhs4njz2dvpry3dqkkj8v62kc49xy6-ungoogled-chromium-73.0.3683.103-0.4c7fb6d.drv.bz2'.
guix system: error: build of `/gnu/store/1kfhs4njz2dvpry3dqkkj8v62kc49xy6-ungoogled-chromium-73.0.3683.103-0.4c7fb6d.drv' failed

Log
/var/log/guix/drvs/1k/fhs4njz2dvpry3dqkkj8v62kc49xy6-ungoogled-chromium-73.0.3683.103-0.4c7fb6d.drv.bz2
is here
http://www.filedropper.com/fhs4njz2dvpry3dqkkj8v62kc49xy6-ungoogled-chromium-7303683103-04c7fb6ddrv
and again
https://nofile.io/f/fwp7JUkF2U5/fhs4njz2dvpry3dqkkj8v62kc49xy6-ungoogled-chromium-73.0.3683.103-0.4c7fb6d.drv.bz2
April 12, 2019 10:17 AM, znavko <at> disroot.org (mailto:znavko <at> disroot.org) wrote:
My bug report is this https://github.com/Eloston/ungoogled-chromium/issues/730 (https://github.com/Eloston/ungoogled-chromium/issues/730)

During update with `guix pull && guix package -u` ungoogled-chromium build process stops on build derivation on 84% three times in a row.

$ guix describe
Generation 94 Apr 11 2019 21:13:38 (current)
guix a6de569
repository URL: https://git.savannah.gnu.org/git/guix.git (https://git.savannah.gnu.org/git/guix.git)
branch: master
commit: a6de569ea224a2f482c4d13c5f62240d1b1543a0

$ chromium --version
Chromium 73.0.3683.86

It shows this error message http://0x0.st/zNo0.jpg (http://0x0.st/zNo0.jpg)
"A script on this page may be busy, or it have stopped responding...
Script:chrome://global/content/bindings/popup.xml:276"

[Message part 2 (text/html, inline)]

Message #11 received at 35243 <at> debbugs.gnu.org (full text, mbox):

From: Christopher Baines <mail <at> cbaines.net>
To: znavko <at> disroot.org
Cc: 35243 <at> debbugs.gnu.org
Subject: Re: bug#35243: ungoogled-chromium build stops and freezes the system
Date: Fri, 12 Apr 2019 19:54:20 +0100

[Message part 1 (text/plain, inline)]

znavko <at> disroot.org writes:

> My bug report is this https://github.com/Eloston/ungoogled-chromium/issues/730
>
> During update with `guix pull && guix package -u` ungoogled-chromium build process stops on build derivation on 84% three times in a row.

What does your system memory and swap look like at that point,
ungoogled-chromium requires quite a lot of memory to build.

If this is indeed an issue, you might be able to reduce the peak memory
requirement by reducing the number of cores used through --cores.

[signature.asc (application/pgp-signature, inline)]

Message #14 received at 35243 <at> debbugs.gnu.org (full text, mbox):

From: znavko <at> disroot.org
To: "Christopher Baines" <mail <at> cbaines.net>
Cc: 35243 <at> debbugs.gnu.org
Subject: Re: bug#35243: ungoogled-chromium build stops and freezes the system
Date: Fri, 12 Apr 2019 19:12:32 +0000

# free -m
              total        used        free      shared  buff/cache   available
Mem:           7864        1419        3597         162        2847        6082
Swap:          2168         261        1907

--cores - did not use this before. chromium is not necessary for me, just tried. I think, its memory consumption is the worst thing I know about linux software, worse than systemd multifunctional extra-total covering.


April 12, 2019 7:00 PM, "Christopher Baines" <mail <at> cbaines.net> wrote:

> znavko <at> disroot.org writes:
> 
>> My bug report is this https://github.com/Eloston/ungoogled-chromium/issues/730
>> 
>> During update with `guix pull && guix package -u` ungoogled-chromium build process stops on build
>> derivation on 84% three times in a row.
> 
> What does your system memory and swap look like at that point,
> ungoogled-chromium requires quite a lot of memory to build.
> 
> If this is indeed an issue, you might be able to reduce the peak memory
> requirement by reducing the number of cores used through --cores.

Message #17 received at 35243 <at> debbugs.gnu.org (full text, mbox):

From: random user via web <issues.guix.gnu.org <at> elephly.net>
To: 35243 <at> debbugs.gnu.org
Subject: ungoogled-chromium build stops and freezes the system
Date: Mon, 18 May 2020 09:08:24 +0200

Hello.

From what I can tell from the closed bug report filed upstream,
https://github.com/Eloston/ungoogled-chromium/issues/730
 
commit 9a2e5fe5fdcc6ea848ceeefa0f70147dfb360639
originally tried to address the thrashing of end user systems
by disabling parallel-builds and

commit 6a489839a8852dc3428c53b0d35ead32e06dc1ac
incorporated the "jumbo_file_merge_limit" fix and
re-enabled parallel-builds which looks to have fixed this reported bug at the time.

(side note: since it looks like things have changed since then)
commit f613d459be9a91ca778d1a2d5ece941ee21469b5
removed the "jumbo" stuff when ungoogled-chromium was updated to version 80.0.3987.116 
and switched to use clang to build it.

Close?

Message #22 received at 35243-done <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: 35243-done <at> debbugs.gnu.org
Date: Mon, 18 May 2020 14:07:24 -0400

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.