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

Error about recursive nextTick under high load #369

Open
ben-ng opened this issue May 24, 2013 · 2 comments
Open

Error about recursive nextTick under high load #369

ben-ng opened this issue May 24, 2013 · 2 comments
Labels

Comments

@ben-ng
Copy link

ben-ng commented May 24, 2013

Been noticing this warning while running my front-end test suite. It makes about 50 requests per second and I get a barrage of these errors every 50 or so tests so it's not that readily reproducible...

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

Not really sure what to do about it, so I'm hoping it's just a deprecated method being called and an easy fix!

@mde
Copy link
Contributor

mde commented May 24, 2013

We don't use nextTick anywhere in the Geddy codebase, so it's in a dependency somewhere. Looks like it's used extensively in both async_testing and in mongodb-wrapper. I guess the error means it's getting invoked recursively somewhere. Hope that will help you narrow it -- seems like when you upgrade Node the next time, whatever it is, is going to break.

@ben-ng
Copy link
Author

ben-ng commented May 24, 2013

yup. i'm switching to postgres soon so we'll see if the problem persists.

my hunch is that it's in the ancient mongodb-wrapper version we're forced to use...

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

No branches or pull requests

2 participants