Skip to content

Crash with Node.js v10.5.0 #21591

Closed
Closed

Description

  • Version: v10.5.0
  • Platform: Windows 10 x64
  • Subsystem: /

Here is the bug I noticed today. This code

(_=>_(_))(_=>eval(`(${_})(${_})`))

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.

sorry for bad english

Activity

  1. mscdex commented on Jun 29, 2018

    @mscdex
    Contributor

    FWIW it doesn't crash for me on Linux with no special node parameters.

  2. jasnell commented on Jun 29, 2018

    @jasnell
    Member

    Running this within the repl, I get a proper (if not extremely verbose) error.

  3. vsemozhetbyt commented on Jun 29, 2018

    @vsemozhetbyt
    Contributor

    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.

  4. added
    windowsIssues and PRs related to the Windows platform.
    on Jul 1, 2018
  5. bzoz commented on Jul 5, 2018

    @bzoz
    Contributor

    -1073741571 is 0xC00000FD which is stack overflow

  6. gireeshpunathil commented on Jan 2, 2020

    @gireeshpunathil
    Member

    this is fixed via #26832 . Closing, pls re-open if I am wrong

  7. Hakerh400 commented on Jan 2, 2020

    @Hakerh400
    Contributor

    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.

  8. gireeshpunathil commented on Jan 2, 2020

    @gireeshpunathil
    Member

    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.

  9. Hakerh400 commented on Apr 27, 2020

    @Hakerh400
    Contributor

    Does not reproduce on master and in v14.0.0. If nobody can reproduce on master I think this can be closed.

  10. juanarbol commented on May 2, 2020

    @juanarbol
    Member

    Does not reproduce on master and in v14.0.0. If nobody can reproduce on master I think this can be closed.

    Thank you @Hakerh400, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    windowsIssues and PRs related to the Windows platform.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions