daohualiuxiang
/
node
mirror of https://github.com/nodejs/node.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
node/test/pummel/test-next-tick-infinite-cal...

17 lines
341 B
JavaScript
Raw Normal View History

test: enable linting for tests Enable linting for the test directory. A number of changes was made so all tests conform the current rules used by lib and src directories. The only exception for tests is that unreachable (dead) code is allowed. test-fs-non-number-arguments-throw had to be excluded from the changes because of a weird issue on Windows CI. PR-URL: https://github.com/nodejs/io.js/pull/1721 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
2015-05-19 19:00:06 +08:00
'use strict';
test: remove unnecessary assignments common.js needs to be loaded in all tests so that there is checking for variable leaks and possibly other things. However, it does not need to be assigned to a variable if nothing in common.js is referred to elsewhere in the test. PR-URL: https://github.com/nodejs/node/pull/4408 Reviewed-By: James M Snell <jasnell@gmail.com>
2015-12-24 08:02:12 +08:00
require('../common');
node: allow nextTick infinite recursion Removing the depth counter while processing the nextTickQueue made it possible to run out of memory if in an infinite recursive loop using nextTick(). There was also an edge case where too many callbacks were pushed onto the nextTickQueue, while not actually being recursive. This is being done to prevent possible cryptic FATAL ERROR messages from popping up, and issues being posted about them.
2013-11-22 06:41:40 +08:00
test: use eslint to fix var->const/let Manually fix issues that eslint --fix couldn't do automatically. PR-URL: https://github.com/nodejs/node/pull/10685 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Roman Reiss <me@silverwind.io>
2017-01-08 21:19:00 +08:00
let complete = 0;
node: allow nextTick infinite recursion Removing the depth counter while processing the nextTickQueue made it possible to run out of memory if in an infinite recursive loop using nextTick(). There was also an edge case where too many callbacks were pushed onto the nextTickQueue, while not actually being recursive. This is being done to prevent possible cryptic FATAL ERROR messages from popping up, and issues being posted about them.
2013-11-22 06:41:40 +08:00
// This will fail with:
// FATAL ERROR: JS Allocation failed - process out of memory
// if the depth counter doesn't clear the nextTickQueue properly.
(function runner() {
if (1e8 > ++complete)
process.nextTick(runner);
}());
setImmediate(function() {
console.log('ok');
});