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

Exception 'RangeError: Maximum call stack size exceeded' #5

Closed
IvanGoncharov opened this issue Mar 11, 2015 · 3 comments
Closed

Exception 'RangeError: Maximum call stack size exceeded' #5

IvanGoncharov opened this issue Mar 11, 2015 · 3 comments

Comments

@IvanGoncharov
Copy link
Contributor

I'm trying to deference swagger file for Google Drive service.
It's actually common problem for most of Google services.
I disable all options except for 'resolve$Refs' option.
I observing following output:

(node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.
...
(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

@JamesMessinger
Copy link
Member

Thank you for letting me know about this. What platform are you running on (Windows, OSX, Linux)? And what version of Node? To find out what version of Node you're running, type node --version at a command prompt.

@IvanGoncharov
Copy link
Contributor Author

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
$ node --version
v0.10.25

@JamesMessinger
Copy link
Member

I wasn't able to reproduce the same error message that you got, but I did get other errors when I tested the Swagger file that you linked to. All of those errors are now fixed and have been tested on Node 0.10.x, 0.11.x, and 0.12.x on Mac, Windows, and Linux. Please re-test on your environment using Swagger Parser v2.2.9. If you still get errors, please re-open this issue and I'll get 'em fixed.

Thanks!

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

No branches or pull requests

2 participants