litespeedtech / litespeedtech/third-party
make -j4 leads to OOM killer when not enough RAM
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Building BoringSSL on a VM with 1GB of memory can lead to compilation failing because the kernel will kill one of the compiler processes.
(Another problem is thrashing: if swap space is configured and has to be used, the compilation will slow down to a crawl.)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reproducing the make -j4 BoringSSL build on a 1GB VM and inspect the build configuration and parallelism settings; the issue does not define a target fix or acceptance criteria, so the desired behavior needs clarification first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100