Chromium 71 compile causing system lock

NathanZachary · Moderator Joined: 30 Jan 2007 Posts: 2605

Hello all,

I just wanted to see if anyone else has run into this problem or not. When I compile any version of Chromium 71, it will lock my entire system part of the way through. At first, I thought that it was something strange about my workstation, but it just happened on my laptop as well. Here's the emerge output from my workstation (laptop is currently locked):

Jaglover · Posted: Fri Nov 09, 2018 4:17 am Post subject:

Guessing ... you may be low on resources, jumbo-build really eats them up.
_________________
My Gentoo installation notes.
Please learn how to denote units correctly!

NathanZachary · Moderator Joined: 30 Jan 2007 Posts: 2605

Thanks for the response. I would tend to agree if it were only happening on my laptop (with fairly low specs). On my desktop, though, I have 24 GiB of RAM which should be more than sufficient. On my laptop, after waiting a long enough time, I was able to get my Openbox environment to reappear, but it has been frozen since (the clock isn't changing). When I move the mouse, it will eventually catch up. So, I'm not really sure what's going on here, but it doesn't happen with the Chromium 70 builds.
_________________
“Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio---

big · Tux's lil' helper Joined: 18 Jan 2007 Posts: 87

The same issue here!
The Building ate all memory then yielded a bug warning. It's weird the building would continue, and finally failed with a ninja sub-command error.
There would be no response since high memory usage, however it would recover from that.

Hund · Apprentice Joined: 18 Jul 2016 Posts: 218 Location: Sweden

I also had issues with the system running out of memory when compiling qtwebengine. I solved it by adding this line to my make.conf:

NathanZachary · Moderator Joined: 30 Jan 2007 Posts: 2605

If that's the case, then switching back to using -jumbo-build should fix the problem. However, that doesn't seem like a good solution to me. 24GiB of memory should be more than enough for a build of Chromium with jumbo-build enabled. This would be a serious regression from Chromium 70. If there is a consensus, then I will file a bug for tracking.

Thanks!

Cheers,
Nathan Zachary
_________________
“Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio---

Hund · Apprentice Joined: 18 Jul 2016 Posts: 218 Location: Sweden

Jaglover · Posted: Fri Nov 09, 2018 6:31 pm Post subject:

Another factor to consider is ninja, I've read it can default to rather insane job settings. It is not controlled by MAKEOPTS variable, it has its own, I think it is NINJA_FLAGS but you better verify it before using.
_________________
My Gentoo installation notes.
Please learn how to denote units correctly!

NathanZachary · Moderator Joined: 30 Jan 2007 Posts: 2605

I guess that my point here is for typical users, having a Chromium compile essentially crash the system isn't a good approach. We need to figure out what some sane expectations are for the build, and then at least have some Portage checks before continuing.
_________________
“Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio---

big · Tux's lil' helper Joined: 18 Jan 2007 Posts: 87

https://forums.gentoo.org/viewtopic-t-1086548.html
_________________
be big,no bug

pjp · Administrator Joined: 16 Apr 2002 Posts: 20067

NeddySeagoon · Posted: Sat Nov 10, 2018 9:49 am Post subject:

big,

NathanZachary · Moderator Joined: 30 Jan 2007 Posts: 2605

Wow, 24 GiB of RAM and it still failed (froze) with jumbo_file_merge_limit set to 75. I guess I'll try again with 50:

NathanZachary · Moderator Joined: 30 Jan 2007 Posts: 2605

Failed with the cap set at 50 as well. Either that environment variable is not actually being set, or it somehow still needs to be lower. Maybe the jumbo-build flag should be disabled for now. I just don't understand how there was such a dramatic change between Chromium 70 and 71.
_________________
“Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio---

mikexx · n00b Joined: 24 Aug 2018 Posts: 53

Same issue here, I think.
During the compile process my laptop runs out of memory (16GB )and then the laptop works very slow. It takes more than one hour to unlock the laptop or do any other operation. First I thought the swap partition is not used, but it is.

Best
mike

NathanZachary · Moderator Joined: 30 Jan 2007 Posts: 2605

Filed bug 671168 to discuss options and track progress.
_________________
“Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio---

big · Tux's lil' helper Joined: 18 Jan 2007 Posts: 87

chrisyu · Apprentice Joined: 10 Apr 2003 Posts: 207 Location: China

Jaglover · Posted: Wed Dec 26, 2018 11:38 pm Post subject:

The variable for ninja is NINJAOPTS, otherwise it tends to default to the number of cores +2.

https://devmanual.gentoo.org/eclass-reference/ninja-utils.eclass/
_________________
My Gentoo installation notes.
Please learn how to denote units correctly!

erg_samowzbudnik · Posted: Sun Dec 30, 2018 4:57 pm Post subject:

I have similar issue only system froze for good. Without jumbo-build. May have been overheating.

Now, case open and with jumbo-build it some times freezes, some times fails.

when I
USE="jumbo-build" emerge -a chromium
it wants to do the right thing,

but when I put this use flag in /etc/portage/env/chromium.conf (EXTRA_GN="use_jumbo_build=true") it'll try emerging without jumbo-build set.

Therefore I imagine setting jumbo_file_merge_limit there probably does not work neither. What am I doing wrong?

(16G of ram, i7-3630QM 2.4GHz, MAKEOPST -j9 -l

Tom_ · Guru Joined: 20 May 2004 Posts: 444 Location: France

I had the same issue on my desktop (Intel i5 2500k 4 cores and 20GB of ram).

Thanks to this thread, I managed to build Chromium 71.

I used the following settings :
thomas@gentoo ~ % cat /etc/portage/env/chromium.conf
EXTRA_GN="jumbo_file_merge_limit=25"
MAKEOPTS="-j3"

Last compile time was :
Tue Jan 1 12:58:44 2019 >>> www-client/chromium-71.0.3578.80
merge time: 2 hours, 39 minutes and 33 seconds.

Thank you Gentoo forums for helping!

Chromium has become a monster ...

erg_samowzbudnik · Posted: Thu Jan 03, 2019 1:01 pm Post subject:

Well my bad, build fail was due to not enough RAM in this case.
I have /dev/tmp/portage on tmpfs, that beast takes up more than 12G of space - by the way it made me notice that my crypt-swap doesn't mount.
Made an exception for chromium to place its temp files on disk and it built fine.

big · Tux's lil' helper Joined: 18 Jan 2007 Posts: 87

Switching back to use Clang instead of GCC can also solve this issue.I've successfully compiled ver. 72 with CCache enabled
Just need to set CHROMIUM_FORCE_CLANG="yes"
_________________
be big,no bug

sgdavis · n00b Joined: 21 Aug 2019 Posts: 9

sgdavis · n00b Joined: 21 Aug 2019 Posts: 9

I just tried MAKEOPTS=-j2 and after that both MAKEOPTS and NINJAOPTS=-j2... still locked up both times. (only tried jumbo build though).

I'm going to just set CHROMIUM_FORCE_CLANG="yes" in my environment and see if that works. I'll keep you updated!