daohualiuxiang
/
node
mirror of https://github.com/nodejs/node.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
node/test/message/max_tick_depth_trace.out

38 lines
1.0 KiB
Plaintext
Raw Normal View History

Print warning when maxTickDepth is reached
2012-10-30 01:31:50 +08:00
tick 20
tick 19
tick 18
tick 17
tick 16
tick 15
tick 14
tick 13
tick 12
core: Remove the nextTick for running the main file 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
2013-02-28 03:24:02 +08:00
tick 11
Print warning when maxTickDepth is reached
2012-10-30 01:31:50 +08:00
Trace: (node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.
test: Update message tests for streams2
2012-12-15 09:43:02 +08:00
at maxTickWarn (node.js:*:*)
src: domain should not replace nextTick function Previously if you cached process.nextTick and then require('domain') subsequent nextTick() calls would not be caught because enqueued functions were taking the wrong path. This keeps nextTick to a single function reference and changes the implementation details after domain has been required.
2014-03-04 08:27:58 +08:00
at process._nextTick [as _currentTickHandler] (node.js:*:*)
core: Remove the nextTick for running the main file 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
2013-02-28 03:24:02 +08:00
at process.nextTick (node.js:*:*)
test: Update message tests for streams2
2012-12-15 09:43:02 +08:00
at f (*test*message*max_tick_depth_trace.js:*:*)
core: Remove the nextTick for running the main file 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
2013-02-28 03:24:02 +08:00
at process._tickCallback (node.js:*:*)
at Function.Module.runMain (module.js:*:*)
at startup (node.js:*:*)
at node.js:*:*
Print warning when maxTickDepth is reached
2012-10-30 01:31:50 +08:00
tick 10
tick 9
tick 8
tick 7
tick 6
tick 5
tick 4
tick 3
tick 2
core: Remove the nextTick for running the main file 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
2013-02-28 03:24:02 +08:00
tick 1
Print warning when maxTickDepth is reached
2012-10-30 01:31:50 +08:00
Trace: (node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.
test: Update message tests for streams2
2012-12-15 09:43:02 +08:00
at maxTickWarn (node.js:*:*)
src: domain should not replace nextTick function Previously if you cached process.nextTick and then require('domain') subsequent nextTick() calls would not be caught because enqueued functions were taking the wrong path. This keeps nextTick to a single function reference and changes the implementation details after domain has been required.
2014-03-04 08:27:58 +08:00
at process._nextTick [as _currentTickHandler] (node.js:*:*)
core: Remove the nextTick for running the main file 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
2013-02-28 03:24:02 +08:00
at process.nextTick (node.js:*:*)
test: Update message tests for streams2
2012-12-15 09:43:02 +08:00
at f (*test*message*max_tick_depth_trace.js:*:*)
process: separate nextTick domain logic It's cleaner to only load domain ticker logic when the domains are being used. This makes execution slightly quicker in both cases, and simpler from the spinner since there is no need to check if the latest callback requires use of domains.
2013-02-28 03:46:35 +08:00
at process._tickCallback (node.js:*:*)
process: streamlining tick callback logic * Callbacks from spinner now calls its own function, separate from the tickCallback logic * MakeCallback will call a domain specific function if a domain is detected * _tickCallback assumes no domains, until nextTick receives a callback with a domain. After that _tickCallback is overridden with the domain specific implementation. * _needTickCallback runs in startup() instead of nextTick (isaacs) * Fix bug in _fatalException where exit would be called twice (isaacs) * Process.domain has a default value of null * Manually track nextTickQueue.length (will be useful later) * Update tests to reflect internal api changes
2013-02-07 09:26:18 +08:00
at process._tickFromSpinner (node.js:*:*)
Print warning when maxTickDepth is reached
2012-10-30 01:31:50 +08:00
tick 0