You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in Chrome throws RangeError: Maximum call stack size exceeded, in Firefox throws InternalError: too much recursion, but in Node.js crashes the process with no warnings or errors. Tried reducing max old space size and also tried reducing stack size, but the bug persists.
Issue #26829 is unrelated (as explained in #26829 (comment)) and thus #26832 is also unrelated. I can confirm that this issue still reproduces (on master) on some platforms, including windows 8.1
The real issue is v8:8053. I reported it more than a year ago, they confirmed the issue, but still no updates. Note that the issue also reproduces in Chrome.
thanks @Hakerh400 for the explanation. seeing the linked issue, and seeing that this is not happening in mac where I tested, I thought this is fixed. re-opening.
Activity
mscdex commentedon Jun 29, 2018
FWIW it doesn't crash for me on Linux with no special node parameters.
jasnell commentedon Jun 29, 2018
Running this within the repl, I get a proper (if not extremely verbose) error.
vsemozhetbyt commentedon Jun 29, 2018
For me, on Windows 7 x64, this crashes REPL with no errors on 06.14.3, 08.11.3, 10.5.0, last nightly and canary.
bzoz commentedon Jul 5, 2018
-1073741571is0xC00000FDwhich is stack overflowgireeshpunathil commentedon Jan 2, 2020
this is fixed via #26832 . Closing, pls re-open if I am wrong
Hakerh400 commentedon Jan 2, 2020
Issue #26829 is unrelated (as explained in #26829 (comment)) and thus #26832 is also unrelated. I can confirm that this issue still reproduces (on master) on some platforms, including windows 8.1
The real issue is v8:8053. I reported it more than a year ago, they confirmed the issue, but still no updates. Note that the issue also reproduces in Chrome.
gireeshpunathil commentedon Jan 2, 2020
thanks @Hakerh400 for the explanation. seeing the linked issue, and seeing that this is not happening in mac where I tested, I thought this is fixed. re-opening.
Hakerh400 commentedon Apr 27, 2020
Does not reproduce on master and in v14.0.0. If nobody can reproduce on master I think this can be closed.
juanarbol commentedon May 2, 2020
Thank you @Hakerh400, closing.