Skip to content

Commit b2e72c0

Browse files
Noah RoseMyles Borins
authored andcommitted
doc: clarify exceptions during uncaughtException
PR-URL: #5180 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Benjamin Gruenbaum <inglor@gmail.com> Reviewed-By: Roman Reiss <me@silverwind.io>
1 parent b639c33 commit b2e72c0

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

doc/api/process.markdown

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -112,6 +112,10 @@ Do *not* use it as the Node.js equivalent of `On Error Resume Next`. An
112112
unhandled exception means your application - and by extension Node.js itself -
113113
is in an undefined state. Blindly resuming means *anything* could happen.
114114

115+
Exceptions thrown from within the event handler will not be caught. Instead the
116+
process will exit with a non zero exit code and the stack trace will be printed.
117+
This is to avoid infinite recursion.
118+
115119
Think of resuming as pulling the power cord when you are upgrading your system.
116120
Nine out of ten times nothing happens - but the 10th time, your system is bust.
117121

0 commit comments

Comments
 (0)