Skip to content

domains: emit uncaughtException when appropriate - #3640

Closed
misterdjules wants to merge 1 commit into
nodejs:masterfrom
misterdjules:fix-issue-3607-master
Closed

domains: emit uncaughtException when appropriate#3640
misterdjules wants to merge 1 commit into
nodejs:masterfrom
misterdjules:fix-issue-3607-master

Conversation

@misterdjules

Copy link
Copy Markdown

Fix node exiting due to an exception being thrown rather than emitting
an 'uncaughtException' event on the process object when no error
handler is set on the domain within which an error is thrown and an
'uncaughtException' event listener is set on the process.

Fixes#3607.

/cc @nodejs/tsc @nodejs/collaborators.

@misterdjulesmisterdjules added the domain Issues and PRs related to the domain subsystem. label Nov 3, 2015
Fix node exiting due to an exception being thrown rather than emitting
an `'uncaughtException'` event on the process object when no error
handler is set on the domain within which an error is thrown and an
`'uncaughtException'` event listener is set on the process.
Fixesnodejs#3607.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be test-domain-uncaught-exception.js? Seems more explicit.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, renamed in #3654.

@misterdjules

Copy link
Copy Markdown
Author

Closing in favor of #3654.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

domainIssues and PRs related to the domain subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@misterdjules@Fishrock123@mscdex@jasnell