Bug#956211: [Pkg-javascript-devel] Bug#956211: Bug#956211: [Re: nodejs 10 segfaults when running webpack on gitlab 12.9.2]
Le ven. 10 avr. 2020 à 21:15, Pirate Praveen a
écrit :
> Control: reassign -1 gitlab
> Control: tags -1 -wontfix
>
> On Sat, Apr 11, 2020 at 12:32 am, Pirate Praveen
> wrote:
> >
> >
> > On Fri, Apr 10, 2020 at 8:58 pm, Jérémy Lal
> > wrote:
> >>
> >>
> >> Le ven. 10 avr. 2020 à 20:50, Pirate Praveen
> >> a écrit :
> >>>
> >>>
> >>> On Fri, Apr 10, 2020 at 7:35 pm, Jérémy Lal
> >>> 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.
> >>
> >
> > I will try this, probably tomorrow.
> >
>
> runuser -u ${gitlab_user} -- sh -c
> 'NODE_OPTIONS="--max-old-space-size=2048" webpack
> --max-old-space-size=16384 --config config/webpack.config.js'
>
> This worked. Thanks a lot.
>
Nice. My bad for having "googled" the answer.
Of course you need to remove the useless --max-old-space-size in your line.
'NODE_OPTIONS="--max-old-space-size=2048" webpack
--config config/webpack.config.js
but i bet you already noticed that.
>>>
> >>> > 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 ?
> >>
> > If you are okay setting up gitlab from experimental on an lxc or vm
> > then instructions are here https://wiki.debian.org/gitlab
> >
> > Else I can set it up on a test VPS and give you access, possibly
> > tomorrow.
>
Well, if it worked, i won't bother and you shouldn't either.
Anyway i'm cool with following the wiki.
Jérémy
Bug#956211: [Pkg-javascript-devel] Bug#956211: Bug#956211: [Re: nodejs 10 segfaults when running webpack on gitlab 12.9.2]
Control: reassign -1 gitlab
Control: tags -1 -wontfix
On Sat, Apr 11, 2020 at 12:32 am, Pirate Praveen
wrote:
On Fri, Apr 10, 2020 at 8:58 pm, Jérémy Lal
wrote:
Le ven. 10 avr. 2020 à 20:50, Pirate Praveen
a écrit :
On Fri, Apr 10, 2020 at 7:35 pm, Jérémy Lal
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.
I will try this, probably tomorrow.
runuser -u ${gitlab_user} -- sh -c
'NODE_OPTIONS="--max-old-space-size=2048" webpack
--max-old-space-size=16384 --config config/webpack.config.js'
This worked. Thanks a lot.
> 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 ?
If you are okay setting up gitlab from experimental on an lxc or vm
then instructions are here https://wiki.debian.org/gitlab
Else I can set it up on a test VPS and give you access, possibly
tomorrow.
Jérémy
--
Pkg-javascript-devel mailing list
pkg-javascript-de...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Processed: Re: [Pkg-javascript-devel] Bug#956211: Bug#956211: [Re: nodejs 10 segfaults when running webpack on gitlab 12.9.2]
Processing control commands: > reassign -1 gitlab Bug #956211 [nodejs] nodejs 10 segfaults when running webpack on gitlab 12.9.2 - FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory Bug reassigned from package 'nodejs' to 'gitlab'. No longer marked as found in versions nodejs/10.15.2~dfsg-2 and nodejs/10.19.0~dfsg-3. Ignoring request to alter fixed versions of bug #956211 to the same values previously set > tags -1 -wontfix Bug #956211 [gitlab] nodejs 10 segfaults when running webpack on gitlab 12.9.2 - FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory Removed tag(s) wontfix. -- 956211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#956211: [Pkg-javascript-devel] Bug#956211: [Re: nodejs 10 segfaults when running webpack on gitlab 12.9.2]
On Fri, Apr 10, 2020 at 8:58 pm, Jérémy Lal wrote:
Le ven. 10 avr. 2020 à 20:50, Pirate Praveen
a écrit :
On Fri, Apr 10, 2020 at 7:35 pm, Jérémy Lal
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.
I will try this, probably tomorrow.
> 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 ?
If you are okay setting up gitlab from experimental on an lxc or vm
then instructions are here https://wiki.debian.org/gitlab
Else I can set it up on a test VPS and give you access, possibly
tomorrow.
Jérémy
Bug#956211: [Pkg-javascript-devel] Bug#956211: [Re: nodejs 10 segfaults when running webpack on gitlab 12.9.2]
Le ven. 10 avr. 2020 à 20:50, Pirate Praveen a
écrit :
>
>
> On Fri, Apr 10, 2020 at 7:35 pm, Jérémy Lal 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
Bug#956211: [Pkg-javascript-devel] Bug#956211: [Re: nodejs 10 segfaults when running webpack on gitlab 12.9.2]
On Fri, Apr 10, 2020 at 7:35 pm, Jérémy Lal 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?
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.
Bug#956211: [Re: nodejs 10 segfaults when running webpack on gitlab 12.9.2]
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. Nodejs applications using high memory must use that kind of workaround. Jérémy. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nodejs depends on: ii libc6 2.30-4 ii libnode64 10.19.0~dfsg-3 Versions of packages nodejs recommends: ii ca-certificates 20190110 ii nodejs-doc 10.19.0~dfsg-3 Versions of packages nodejs suggests: ii npm 6.14.4+ds-1 -- no debconf information
