[Pkg-javascript-devel] Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

[Thorsten Glaser]

James Addison dixit:

>So: a fix here won't achieve stack capacity equality across

No. The fix you proposed won’t achieve that but others would
improve the situation much more, so that equality across arches
won’t need to matter any more.

>Or, to put it another way: applying an increase (either static or
>dynamic, either ARM-specific or across all architectures) for stack
>size determination would move the problem, and another architecture
>would take the place of "architecture where RangeError can occur in
>code x that doesn't occur on other architectures".

Yes, but given the usual ulimit, the new limit would be 4+ times
the old one, much much harder to reach.

>it, though - and based on their current policy, NodeJS upstream seem
>unlikely to accept it since they don't want to modify their vendored
>V8.

AIUI that’s not necessary because you can already set the stack
limit with a nodejs command line option. The patch could just
set the limit, using the same facility that CLI option uses, if
that option isn’t given (or before it is processed).

bye,
//mirabilos
-- 
(gnutls can also be used, but if you are compiling lynx for your own use,
there is no reason to consider using that package)
	-- Thomas E. Dickey on the Lynx mailing list, about OpenSSL