You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Building firefox is always a challenge to computers which are not fast enough. I am building a customized firefox for Arch Linux with OBS at here. But it will eats all the memory at linking stage finally and throw an OOM error. Checking its build log shows that the building system tries to use 50GB memory and there is only 44GB at maximum available here.
It seems that I can limit processor cores by using lower memory size, but it is not enough. For example, I have tried to use 8GB memory and there are still 4 cpu cores, while I want to use 2 cores or less only.
Firefox's build system provides an option called MOZ_PARALLEL_BUILD to limit build number in parallel but it does not seem to limit linker processes number, which results that too many cpu cores are used when linking and the memory space is not enough to finish linking.
Describe the solution you'd like
Adding more memory is always the simplest solution, but OBS's workers seem to only have 40GB physical memory and 4GB swap at most. So the second solution is here: using less cpu cores. But I tried setting jobs and MOZ_PARALLEL_BUILD, both are not effective enough. They did limit build number but there is no limit to linker number.
So my last thought is allowing us limiting cpu cores, but processors in _constraints seems to be a minimum value, not a maximum value.
Describe alternatives you've considered
Maybe allowing us adding more swap can be another solution? But I completely do not know how to increase swap partition size, it seems the size of swap partition is always 4GB.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Building firefox is always a challenge to computers which are not fast enough. I am building a customized firefox for Arch Linux with OBS at here. But it will eats all the memory at linking stage finally and throw an OOM error. Checking its build log shows that the building system tries to use 50GB memory and there is only 44GB at maximum available here.
It seems that I can limit processor cores by using lower memory size, but it is not enough. For example, I have tried to use 8GB memory and there are still 4 cpu cores, while I want to use 2 cores or less only.
Firefox's build system provides an option called
MOZ_PARALLEL_BUILD
to limit build number in parallel but it does not seem to limit linker processes number, which results that too many cpu cores are used when linking and the memory space is not enough to finish linking.Describe the solution you'd like
Adding more memory is always the simplest solution, but OBS's workers seem to only have 40GB physical memory and 4GB swap at most. So the second solution is here: using less cpu cores. But I tried setting
jobs
andMOZ_PARALLEL_BUILD
, both are not effective enough. They did limit build number but there is no limit to linker number.So my last thought is allowing us limiting cpu cores, but
processors
in_constraints
seems to be a minimum value, not a maximum value.Describe alternatives you've considered
Maybe allowing us adding more swap can be another solution? But I completely do not know how to increase swap partition size, it seems the size of swap partition is always 4GB.
Additional context
N/A
The text was updated successfully, but these errors were encountered: