From: znavko@disroot.org
To: Christopher Baines <mail@cbaines.net>
Cc: 35243@debbugs.gnu.org
Subject: bug#35243: ungoogled-chromium build stops and freezes the system
Date: Fri, 12 Apr 2019 19:12:32 +0000 [thread overview]
Message-ID: <8f77d5d5b3a8c9b96d3a704562584dff@disroot.org> (raw)
In-Reply-To: <87tvf3caw3.fsf@cbaines.net>
# 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.
next prev parent reply other threads:[~2019-04-12 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2020-05-18 7:08 ` random user via web
2020-05-18 18:07 ` bug#35243: (no subject) Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f77d5d5b3a8c9b96d3a704562584dff@disroot.org \
--to=znavko@disroot.org \
--cc=35243@debbugs.gnu.org \
--cc=mail@cbaines.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.