Package: nodejs Followup-For: Bug #1030284 X-Debbugs-Cc: t...@debian.org, reply+aagshfqluldiwi3obwdg6lgb7if7fevbnhheauz...@reply.github.com
mirabilos gesagt: > We know the default ulimits for users in Debian, and they are higher > than the 1 MiB assumed by v8, by quite some factor, so this won’t break > things which are not currently broken (by that exception). This will do > for the release I think. Relaying my understanding of this, so far: An increase in the V8 stack size should not cause earlier-process-exits for any processes that previously ran on Debian systems where the architecture-default-or-greater stack size is configured[1]. In other words: the same-number-or-greater of JavaScript processes should continue to run on any given Debian system where the configured stack size is greater-than-or-equal to the architecture's default, after the V8 stack size limit is increased. And we expect that it should repair a failing reproducible build test for at least one Debian package on arm64. [1] - see limits.conf
