replace process.nextTick with setImmediate to fix 'RangeError: Maximum call stack size exceeded' #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…m call stack size exceeded'
joeferner
added a commit
that referenced
this pull request
Sep 27, 2013
replace process.nextTick with setImmediate to fix 'RangeError: Maximum call stack size exceeded'
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
node-unzip depends on node-pullstream, but unzipping certain archives generates a bunch of:
Followed by:
node-unzip had a similar problem in its own code and fixed it by replacing process.nextTick calls with setImmediate (EvanOxfeld/node-unzip#28). This PR does the same for node-pullstream and fixes the problem unzipping files in my testing.