* bug#35243: ungoogled-chromium build stops and freezes the system
2019-04-12 10:15 bug#35243: ungoogled-chromium build stops and freezes the system znavko
@ 2019-04-12 18:14 ` znavko
2019-04-12 18:54 ` Christopher Baines
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: znavko @ 2019-04-12 18:14 UTC (permalink / raw)
To: 35243
[-- Attachment #1: Type: text/plain, Size: 2308 bytes --]
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@disroot.org (mailto:znavko@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"
[-- Attachment #2: Type: text/html, Size: 2982 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread* bug#35243: ungoogled-chromium build stops and freezes the system
2019-04-12 10:15 bug#35243: ungoogled-chromium build stops and freezes the system znavko
2019-04-12 18:14 ` znavko
@ 2019-04-12 18:54 ` Christopher Baines
2019-04-12 19:12 ` znavko
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Christopher Baines @ 2019-04-12 18:54 UTC (permalink / raw)
To: znavko; +Cc: 35243
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
znavko@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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread* bug#35243: ungoogled-chromium build stops and freezes the system
2019-04-12 10:15 bug#35243: ungoogled-chromium build stops and freezes the system znavko
2019-04-12 18:14 ` znavko
2019-04-12 18:54 ` Christopher Baines
@ 2019-04-12 19:12 ` znavko
2020-05-18 7:08 ` random user via web
2020-05-18 18:07 ` bug#35243: (no subject) Leo Famulari
4 siblings, 0 replies; 6+ messages in thread
From: znavko @ 2019-04-12 19:12 UTC (permalink / raw)
To: Christopher Baines; +Cc: 35243
# 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@cbaines.net> wrote:
> znavko@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.
^ permalink raw reply [flat|nested] 6+ messages in thread* bug#35243: ungoogled-chromium build stops and freezes the system
2019-04-12 10:15 bug#35243: ungoogled-chromium build stops and freezes the system znavko
` (2 preceding siblings ...)
2019-04-12 19:12 ` znavko
@ 2020-05-18 7:08 ` random user via web
2020-05-18 18:07 ` bug#35243: (no subject) Leo Famulari
4 siblings, 0 replies; 6+ messages in thread
From: random user via web @ 2020-05-18 7:08 UTC (permalink / raw)
To: 35243
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?
^ permalink raw reply [flat|nested] 6+ messages in thread* bug#35243: (no subject)
2019-04-12 10:15 bug#35243: ungoogled-chromium build stops and freezes the system znavko
` (3 preceding siblings ...)
2020-05-18 7:08 ` random user via web
@ 2020-05-18 18:07 ` Leo Famulari
4 siblings, 0 replies; 6+ messages in thread
From: Leo Famulari @ 2020-05-18 18:07 UTC (permalink / raw)
To: 35243-done
^ permalink raw reply [flat|nested] 6+ messages in thread
