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

doc: clarify the restrictions of catching an uncaughtException #5180

Closed
wants to merge 3 commits into from
Closed

doc: clarify the restrictions of catching an uncaughtException #5180

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
79b8c2e
doc: clarify the restrictions of catching an uncaughtException
Feb 10, 2016
06f07a6
doc: revise the restrictions of catching an uncaughtException
Feb 10, 2016
6c3714c
doc: revise wording of process termination in uncaughtException event
Feb 11, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions doc/api/process.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,6 +118,10 @@ Do *not* use it as the Node.js equivalent of `On Error Resume Next`. An
unhandled exception means your application - and by extension Node.js itself -
is in an undefined state. Blindly resuming means *anything* could happen.

Exceptions thrown from within the event handler will not be caught. Instead the
process will exit with a non zero exit code and the stack trace will be printed.
This is to avoid infinite recursion.

Think of resuming as pulling the power cord when you are upgrading your system.
Nine out of ten times nothing happens - but the 10th time, your system is bust.

Expand Down