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

Fatal error: Maximum call stack size exceeded #179

Closed
ain opened this issue Mar 26, 2014 · 6 comments
Closed

Fatal error: Maximum call stack size exceeded #179

ain opened this issue Mar 26, 2014 · 6 comments

Comments

@ain
Copy link

ain commented Mar 26, 2014

Transferring from imagemin/imagemin#22 since it's not in the scope of imagemin. It looks like a problem described in caolan/async#75.

Minification throws up on JPEG with:

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

node.js:0
// Copyright Joyent, Inc. and other Node contributors.
^
RangeError: Maximum call stack size exceeded

Running it in conjunction of grunt-contrib-imagemin 0.6.0-pre.

Platform:

Mac OS X 10.8.5
Xcode 5.0
node: v0.10.21
@sindresorhus
Copy link
Member

Try changing

to setImmediate(next);

ain added a commit to interactive-pioneers/grunt-contrib-imagemin that referenced this issue Mar 26, 2014
@vladikoff
Copy link
Member

Please try 0.6.0-pre again by doing npm cache clean && npm install gruntjs/grunt-contrib-imagemin

@ain
Copy link
Author

ain commented Mar 27, 2014

@vladikoff the latest runs into:

Warning: EBADF, write Use --force to continue.
Error: EBADF, write

@sindresorhus' presumption may have been right, still? I'll try our fork in a second, but the issue can be reopened surely.

@ain
Copy link
Author

ain commented Mar 27, 2014

@sindresorhus switching to setImmediate(next); doesn't seem to work either, same EBADF error as above.

@ain
Copy link
Author

ain commented Mar 28, 2014

With exactly the same input, grunt-imgcompress worked.

@jamesplease jamesplease reopened this Mar 28, 2014
@vladikoff
Copy link
Member

Hey @ain!
0.6.0 is out, try that. If you still have the issue could you please share the configuration you are using and maybe share the JPEG you are using as well (if possible).
Also, how many files are you processing?

One occurrence of this error is noted here: http://gruntjs.com/frequently-asked-questions#why-am-i-getting-a-maximum-call-stack-size-exceeded-error

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

4 participants