Bug 198070 - Webkit-gtk is a memory hog during compilation
Summary: Webkit-gtk is a memory hog during compilation
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-21 05:47 PDT by Raymond Jennings
Modified: 2019-05-21 12:26 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Raymond Jennings 2019-05-21 05:47:00 PDT
Is there any way to make webkit-gtk smaller or break it up into multiple modules?

Trying to compile it in gentoo routinely goes into 20 or so gigabytes of memory usage.
Comment 1 Michael Catanzaro 2019-05-21 07:59:22 PDT
Not really, sorry. Use lower -j such as -j1 to limit parallel process for starters. Then experiment with increasing it until you find the highest -j your computer can handle without freezing up.

You can also try -DENABLE_UNIFIED_BUILDS=OFF, but it's usually broken, so you need to be prepared to regularly send a lot of patches to keep this working if you want to try.
Comment 2 Adrian Perez 2019-05-21 12:26:59 PDT
Usually the most critical part of compilation when it comes
to memory usage is linking binaries. Something that helps is
making sure you have the Gold linker installed, and that it
is being used (CMake will print a warning if it was not found,
IIRC). Alternatively, you *might* have better luck with the
lld linker (which uses LLVM), but using it to build WebKitGTK
has not been tested much, so YMMV. I hope this tip helps :-)