doc: clarify exceptions during uncaughtException

PR-URL: #5180 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Fedor Indutny <[email protected]> Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Roman Reiss <[email protected]>
nodejs · Mar 2, 2016 · ec4d6b9 · ec4d6b9
1 parent 972c063
commit ec4d6b9
Showing 1 changed file with 4 additions and 0 deletions.
diff --git a/doc/api/process.markdown b/doc/api/process.markdown
@@ -112,6 +112,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.