aboutsummaryrefslogtreecommitdiff
path: root/test/message/max_tick_depth.out
AgeCommit message (Collapse)Author
2013-05-30process: remove maxTickDepth from _tickCallbackTrevor Norris
Removes the check for maxTickDepth for non-domain callbacks. So a user can starve I/O by setting a recursive nextTick. The domain case is more complex and will be addressed in another commit.
2013-02-27core: Remove the nextTick for running the main fileisaacs
Not necessary, since we can handle the error properly on the first tick now, even if there are event listeners, etc. Additionally, this removes the unnecessary "_needTickCallback" from startup, since Module.loadMain() will kick off a nextTick callback right after it runs the main module. Fix #4856
2012-10-29Print warning when maxTickDepth is reachedisaacs