Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warning Recursive process.nextTick detected then stack overflow #28

Closed
apond opened this issue Jun 25, 2013 · 4 comments · Fixed by #31
Closed

Warning Recursive process.nextTick detected then stack overflow #28

apond opened this issue Jun 25, 2013 · 4 comments · Fixed by #31

Comments

@apond
Copy link

apond commented Jun 25, 2013

For some files I get a slew of messages that look like this:
(node) warning: Recursive process.nextTick detected. This will break in the next
version of node. Please use setImmediate for recursive deferral.
Followed by this:
RangeError: Maximum call stack size exceeded

My node version is:
v0.10.5

My unzip version is:
0.1.8

My code looks like this:
var parse_archive = function(path, callback) {
var unzipParser = unzip.Parse();
var entries = [];
unzipParser.on('close', function() {
console.log("Closing");
callback(null, entries);
});

unzipParser.on('error', function(err, dirPath) {
console.log("Error unzipping " + dirPath);
callback(err);
});

console.log("parse: " + path);
fs.createReadStream(path)
.pipe(unzipParser)
.on('entry', function(entry) {
if (entry.type === "File")
{
entries.push(entry.path);
entry.autodrain();
}
});
};

@asnowfix
Copy link

asnowfix commented Aug 8, 2013

Same problem for me. This is immediately followed by a stack overflow & the node process fails:

ares WARN genZip (node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.
ares WARN genZip 
ares WARN genZip 
ares WARN genZip 
ares WARN genZip RangeError: Maximum call stack size exceeded
ares WARN genZip 

This problem:

  1. does not occur with node 0.8.x.
  2. happens with both 0.1.3 & 0.1.8

@AndersDJohnson
Copy link

Same.
Node v0.10.10
unzip@0.1.8

@satazor
Copy link

satazor commented Sep 1, 2013

JFYI this problem still exists because some of node-unzip's dependencies have the same problem. You can test it by extracting this file: https://github.com/Polymer/polymer/releases/download/v0.0.20130829/polymer-all-v0.0.20130829.zip

@mykmelez
Copy link

JFYI this problem still exists because some of node-unzip's dependencies have the same problem. You can test it by extracting this file: https://github.com/Polymer/polymer/releases/download/v0.0.20130829/polymer-all-v0.0.20130829.zip

I submitted EvanOxfeld/node-pullstream#8 to fix the problem in node-pullstream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants