Building Qt from source with QtWebEngine causing OOM crashes
-
wrote on 26 Feb 2023, 16:56 last edited by
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?
-
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.wrote on 3 Mar 2023, 17:55 last edited by quutee 3 Mar 2023, 17:56I 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. -
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 Does "ninja -j 1" help?
-
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?
wrote on 27 Feb 2023, 10:26 last edited by odelaune -
-
@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.
wrote on 28 Feb 2023, 08:29 last edited by@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 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?
wrote on 28 Feb 2023, 17:54 last edited by quutee@odelaune
ld
receives a kill signal (due to OOM) when linking qtwebcoreengine.so. -
@odelaune
ld
receives a kill signal (due to OOM) when linking qtwebcoreengine.so.wrote on 1 Mar 2023, 05:31 last edited by quutee 3 Jan 2023, 05:31I 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. -
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.wrote on 3 Mar 2023, 17:55 last edited by quutee 3 Mar 2023, 17:56I 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. -
1/8