isaacs 0400571676 domain: Properly exit() on domain disposal ... This addresses #4034. There are two problems happening: 1. The domain is not exited automatically when calling dispose() on it. Then, since the domain is disposed, attempting to exit it again will do nothing. 2. The active domain is stored on process.domain. Since thrown errors call `process.emit('uncaughtException', er)`, and the process is an event emitter with a `.domain` member, it re-enters the domain a second time before calling the error handler, pushing it onto the stack again. Thus, if the handler calls `domain.dispose()`, then the domain is now on the stack twice, and cannot be exited properly. Since the domain is disposed, any subsequent IO will be no-op'ed, since we've declared that this context is done and best forgotten. The solution here is twofold: 1. In EventEmitter.emit, do not enter the domain if `this===process`. 2. Automatically exit the domain when calling `domain.dispose()`.		2012-09-21 09:22:50 -07:00
..
addons	test: update addons .gitignore	2012-05-24 14:07:09 +02:00
disabled
fixtures	fs: don't segfault on deeply recursive stat()	2012-09-14 02:37:51 +02:00
gc	test: use the debug build of node-weak when necessary	2012-06-13 17:58:28 -07:00
internet	Revert "DNS: Support NAPTR queries"	2012-06-16 11:02:49 -07:00
message	test-message: fix message output	2012-08-05 14:33:23 -07:00
pummel	Test client renegotiation attacks on HTTPS	2012-08-29 12:26:28 -07:00
simple	domain: Properly exit() on domain disposal	2012-09-21 09:22:50 -07:00
common.js