OnUncaughtException Integration should allow to not exit the process

[adarnon]

• Review the documentation: https://docs.sentry.io/
• Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• Use the latest release: https://github.com/getsentry/sentry-javascript/releases
• Provide a link to the affected event from your Sentry account

Package + Version

• @sentry/browser
• @sentry/node
• raven-js
• raven-node (raven for node)
• other:

Version:

6.14.3

Description

Node's OnUncaughtException handler has implemented logic to report the exception to Sentry and exit the process. However, exiting the process is not always desirable. If I have a long-running Node server process, I'd want an uncaught exception to be captured, but I don't want the process to exit.

Overriding onFatalError is not enough, because Sentry forcefully kills the process if two uncaught exceptions happen in a row, even if they are unrelated to each other (due to the caughtFirstError variable in the _makeErrorHandler() closure - see onuncaughtexception.ts)

[AbhiPrasad]

Probably best we introduce an option for this. Will backlog, but PRs are welcome to add this functionality!

[maxpain]

Any news?

[Lms24]

Hi, seems like this issue slipped through.
I'm going to close as this as it was fixed by introducing exitEvenIfOtherHandlersAreRegistered (#1661 (comment)). Please feel free to let us know if you think this issue should be repopened.