Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

process: do not directly schedule _tickCallback in _fatalException #17841

Closed
wants to merge 1 commit into from
Closed

process: do not directly schedule _tickCallback in _fatalException #17841

wants to merge 1 commit into from

Commits on Dec 27, 2017

  1. process: do not directly schedule _tickCallback in _fatalException 

    When a process encounters a _fatalException that is caught, it should
schedule execution of nextTicks but not in an arbitrary place of the
next Immediates queue. Instead, add a no-op function to the queue
that will ensure processImmediate runs, which will then ensure
that nextTicks are processed at the end.
    @apapirovski
    apapirovski committed Dec 27, 2017
    Configuration menu
    Copy the full SHA
    5491092 View commit details
    Browse the repository at this point in the history