Created attachment 656528 [details] output emerge --info '=www-client/chromium-84.0.4147.135::gentoo x86_64-pc-linux-gnu-g++: fatal error: Killed signal terminated program cc1plus compilation terminated. ninja: build stopped: subcommand failed. * ERROR: www-client/chromium-84.0.4147.135::gentoo failed (compile phase): * ninja -v -j8 -l0 -C out/Release chrome chromedriver failed * * Call stack: * ebuild.sh, line 125: Called src_compile * environment, line 4344: Called eninja '-C' 'out/Release' 'chrome' 'chromedriver' * environment, line 2041: Called die * The specific snippet of code: * "$@" || die "${nonfatal_args[@]}" "${*} failed"
Created attachment 656530 [details] output of emerge -pqv '=www-client/chromium-84.0.4147.135::gentoo'
Created attachment 656532 [details] build.log
>x86_64-pc-linux-gnu-g++: fatal error: Killed signal terminated program cc1plus Check dmesg, but you almost certainly out of memory errored (OOMed). Run with fewer jobs.
(In reply to Sam James from comment #3) > >x86_64-pc-linux-gnu-g++: fatal error: Killed signal terminated program cc1plus > > Check dmesg, but you almost certainly out of memory errored (OOMed). Run > with fewer jobs. I will try, thanks. If it works, the bug with this ebuild is that * Checking for at least 3 GiB RAM ... [ ok ] * Checking for at least 7 GiB disk space at "/var/tmp/portage/www-client/chromium-84.0.4147.135/temp" ... [ ok ] is not enough then.
3GB is the bare minimum with low jobs (1), it cannot possibly calculate exactly how much memory will be used for your job count and your compiler version and options and your existing memory load (eg is chromium already running with 20 tabs open using 5GB memory?).
