Greg Brail 6eb4d1d15c timer: don't reschedule timer bucket in a domain ...

If two timers run on the same tick, and the first timer uses a domain,
and then catches an exception and disposes of the domain, then the
second timer never runs. (And even if the first timer does not dispose
of the domain, the second timer could run under the wrong domain.)

This happens because timer.js uses "process.nextTick()" to schedule
continued processing of the timers for that tick. However, there was
an exception inside a domain, then "process.nextTick()" runs under
the domain of the first timer function, and will do nothing if
the domain has been disposed.

To avoid this, we temporarily save the value of "process.domain"
before calling nextTick so that it does not run inside any domain.

2014-03-03 17:46:49 -08:00

..

addons

test: modify async native test.js to test for #4820

2013-02-21 13:14:07 -08:00

disabled

Merge remote-tracking branch 'ry/v0.8' into master

2013-02-18 10:21:08 -08:00

fixtures

node: do not ever close stdio

2014-01-30 21:26:19 +04:00

gc

test: use the debug build of node-weak when necessary

2012-06-13 17:58:28 -07:00

internet

test: move two tests from simple/ to internet/

2013-07-20 12:36:33 +02:00

message

src: domain should not replace nextTick function

2014-03-03 16:27:58 -08:00

pummel

fs: make unwatchFile() insensitive to path

2014-02-06 13:04:35 +04:00

simple

timer: don't reschedule timer bucket in a domain

2014-03-03 17:46:49 -08:00

common.js

test: optionally set common.PORT via env variable

2013-03-02 19:09:39 +01:00