Le ven. 10 avr. 2020 à 20:50, Pirate Praveen <prav...@onenetbeyond.org> a
écrit :
>
>
> On Fri, Apr 10, 2020 at 7:35 pm, Jérémy Lal <kapo...@melix.org> wrote:
> > Package: nodejs
> > Version: 10.19.0~dfsg-3
> > Followup-For: Bug #956211
> >
> > Pirate, i repeat, please try
> >
> > webpack --max-old-space-size=4096
> >
> > Or even a higher value. If it works, it's up to gitlab to use that
> > flag.
> >
>
> root@gitlab-buster:/usr/share/gitlab# runuser -u ${gitlab_user} -- sh
> -c 'webpack --max-old-space-size=8192 --config config/webpack.config.js'
>
> I tried 4096, 6144, 8192, 16384 and all failed. How much higher should
> I go?
>
Not further :)
However then maybe that flag has no effect.
Another way to pass the flag is by setting the environment variable:
NODE_OPTIONS="–max-old-space-size=2048"
Then again, runuser need to be told to handle this correctly.
>
> > Nodejs applications using high memory must use that kind of
> > workaround.
>
> I was also exploring if excluding system libraries from babel-loader
> reduces memory footprint.
Yep, i saw that.
Can you give me a quick way to reproduce the OOM error ?
Jérémy
