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.

Sign up for GitHub

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

Jump to bottom

Use setImmediate instead of process.nextTick with latest node versions #40

Closed
dimik opened this issue Aug 19, 2013 · 1 comment
Closed

Use setImmediate instead of process.nextTick with latest node versions #40

dimik opened this issue Aug 19, 2013 · 1 comment

Comments

@dimik
Copy link
Contributor

dimik commented Aug 19, 2013

Hi!
I had an issue with some recursive calls of third party lib.
The log message looks like this:

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

When i have changed nextTick with setImmediate in your Vow code,
it starts fail silently =)
dfilatov added a commit that referenced this issue Aug 19, 2013
@dfilatov
Use setImmediate instead of process.nextTick with latest node versions (
5c76dbc 
#40)
@dfilatov
Copy link
Owner

fixed in 0.3.10

@omgtehlion omgtehlion mentioned this issue Dec 14, 2013
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dfilatov @dimik