projects / platform / upstream / nodejs.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 1a7d3e2) | patch
node: allow nextTick infinite recursion
authorTrevor Norris <trev.norris@gmail.com>
Thu, 21 Nov 2013 22:41:40 +0000 (14:41 -0800)
committerTrevor Norris <trev.norris@gmail.com>
Thu, 21 Nov 2013 23:01:53 +0000 (15:01 -0800)
commit5757642e912c0a4de6476fc766748b6e33ac845b
tree6211f256ee40d3d66657bd168f28f17e6c103369tree | snapshot
parent1a7d3e2b72abdd9a523409324ff7eca27633edf0commit | diff
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.
src/node.js diff | blob | history
test/pummel/test-next-tick-infinite-calls.js [new file with mode: 0644] blob
Domain: Web Framework / Common;