Building Qt from source with QtWebEngine causing OOM crashes

[quutee]

Hi,

I am compiling Qt 5.15.8 from source on Ubuntu 20.04 (8-core/16 GB RAM) with QtWebEngine module enabled. After sometime everything running on the machine closes automatically. It seems ninja (internally used for building chromium) is building on all cores even if I trigger the build using make -j1, and consumes all the memory.

Notice how the CPU usage drops as memory peaks to 100%.

I did not encounter this problem on macOS. Has anyone else faced this issue? Any tips on how to prevent these OOM crashes?

[quutee]

I disabled symbol generation for chromium by adding the following line to qtwebengine/src/core/gn_run.pro to reduce the memory required during linking.

gn_args += symbol_level=0

There's also a flag that can be passed to configure to disable chromium symbols but it didn't work.

[jsulm]

@quutee Does "ninja -j 1" help?

[odelaune]

@quutee
Building QWebEngine is really a nightmare. Please read this post.
The only way I know is to fake the number of CPU available on the system using chcpu. If you do not have sudo right for chcpu then I cannot help you (I am also looking for a solution ...).

[quutee]

@odelaune I do have sudo permissions and was able to build release shared builds by disabling half the cpu cores but shared debug build still fails on the linking step.

[odelaune]

@quutee said in Building Qt from source with QtWebEngine causing OOM crashes:

shared debug build still fails on the linking step.

What is the error you get?

[quutee]

@odelaune ld receives a kill signal (due to OOM) when linking qtwebcoreengine.so.

[quutee]

I added 64GB swap space, but ld still crashes (along with the terminal from which make is run). It doesn't seem to be using swap space much even though I have set swappiness to 100.

[quutee]

I disabled symbol generation for chromium by adding the following line to qtwebengine/src/core/gn_run.pro to reduce the memory required during linking.

gn_args += symbol_level=0

There's also a flag that can be passed to configure to disable chromium symbols but it didn't work.