This has been happening consistently for the past few weeks with both packages, chromium even on the previous stable version, but only on one machine (on another one, both build without a problem). I've tried to reduce the number of parallel jobs, but it didn't make a difference. Reproducible: Always Steps to Reproduce: emerge -1v www-client/chromium emerge -1v dev-qt/qtwebengine Actual Results: build crashes with a segfault Expected Results: build should complete
Created attachment 598520 [details] emerge --info Attaching output of emerge --info.
Please attach the entire build logs to this bug report.1
Created attachment 598524 [details] chromium build.log Attaching the tail of build.log from chromium. (I wasn't upload the full thing after compressing it...)
Ugh, it gets even weirder. I had a running build of qtwebengine today just to give it another go (and to see if it would fail on the same module), and this time it finished successfully – and I forgot to save the log of the previous failed run, so it got deleted automatically. Really sorry about that.
(In reply to Michal Petrucha from comment #3) > Created attachment 598524 [details] > chromium build.log > > Attaching the tail of build.log from chromium. (I wasn't upload the full > thing after compressing it...) Makes me wonder what compression you used. Normally chromium build logs compressed with plain xz will work just fine.
Created attachment 598526 [details] full chromium build.log Oops, my bad. I did try xz before, turns out it was a local permission issue. I swear I'm not always this incompetent with computers.
* Checking for at least 7 GiB disk space at "/var/tmp/portage/www-client/chromium-78.0.3904.108/temp" ... [ !! ] * There is NOT at least 7 GiB disk space at "/var/tmp/portage/www-client/chromium-78.0.3904.108/temp" * * Space constraints set in the ebuild were not met! * The build will most probably fail, you should enhance the space * as per failed tests. How much space is left there? Also you run emerge with 4 parallel jobs enabled, so you might run out of RAM.
RAM is not the issue – this machine has 16G (+16G swap), and, as I wrote before, I did try reducing the number of parallel jobs. At no point did I see memory being exhausted. However, it does appear that the disk space might have been the cause. I recently increased the capacity of /, and now the build succeeded. Even though I didn't see any messages that would indicate disk space being the issue. It's quite weird, I definitely wouldn't expect a segfault to happen as a result of insufficient disk space. Either way, apologies for the noise, looks like it was an error on my end.
