[Pkg-javascript-devel] Bug#1076350: Bug#1076350: nodejs: segfault in node when running browserify script on i386 when building node-chai

[Сергей Сёмин]

I tried to give maximum resources to my VM with Debian Bookworm i386
(recently upgraded to Debian Sid).
I gave 8 GB RAM in VM settings but because of i386 limitations only
4GB actually available in VM.
The problem remains:

root at debian-bookworm-i386:~/node-chai-4.3.7~ds1+~cs9.7.21# free -h
              total        used        free      shared  buff/cache   available
Mem:           3.4Gi       409Mi       3.2Gi       572Ki       153Mi       3.0Gi
Swap:          974Mi          0B       974Mi
root at debian-bookworm-i386:~/node-chai-4.3.7~ds1+~cs9.7.21# node --version
v20.15.1
root at debian-bookworm-i386:~/node-chai-4.3.7~ds1+~cs9.7.21# browserify --version
17.0.0
root at debian-bookworm-i386:~/node-chai-4.3.7~ds1+~cs9.7.21# browserify
       --bare         --outfile chai.js         --standalone chai
   --entry index.js
Segmentation fault (core dumped)
root at debian-bookworm-i386:~/node-chai-4.3.7~ds1+~cs9.7.21# free -h
              total        used        free      shared  buff/cache   available
Mem:           3.4Gi       486Mi       3.1Gi       572Ki       160Mi       3.0Gi
Swap:          974Mi          0B       974Mi

Thank you for your ideas what to check on next step.
At this moment I have workaround when building node-chai - not to call
browserify (a custom patch). Result deb packages are incomplete, but
at this moment I think it is enough for my aims.
This bug I opened just for info, because I thought it can show some
problems in nodejs itself and is interesting because of it.
In case of free time available I'll try to check the next steps you recommended.

Thank you!

пн, 15 июл. 2024 г. в 12:02, Jérémy Lal <kapouer at melix.org>:
>
> Thanks.
>
> It may be that browserify hits a bug by exhausting resources (heap).
> Using another bundler might be a good idea (rollup, webpack, esbuild...).
>
> Upstream doesn't support 32-bits builds on linux, however it does provide 32-bits build for windows.
> If that bug can be reproduced there, it would be awesome, see
> https://nodejs.org/fr/download/prebuilt-binaries
>
> I may have an old windows vm to test this, but I may not have time to do this.