From fa04daa38492855c8533f71977e9f8e83a6e0074 Mon Sep 17 00:00:00 2001 From: Noah Rose Date: Wed, 10 Feb 2016 10:30:30 -0800 Subject: [PATCH] doc: clarify exceptions during uncaughtException PR-URL: https://github.com/nodejs/node/pull/5180 Reviewed-By: James M Snell Reviewed-By: Fedor Indutny Reviewed-By: Sakthipriyan Vairamani Reviewed-By: Benjamin Gruenbaum Reviewed-By: Roman Reiss --- doc/api/process.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/api/process.markdown b/doc/api/process.markdown index 9402788ba15028..c124cfc0a982e6 100644 --- a/doc/api/process.markdown +++ b/doc/api/process.markdown @@ -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.