search

filamentgroup / grunt-criticalcss

Grunt wrapper for criticalcss
MIT License
530 stars 27 forks source link

PhantomJS Error : stdout maxBuffer exceeded #31

Closed gvinson closed 8 years ago

gvinson commented 8 years ago

I have been trying to figure this out all day and can't seem to pinpoint the issue. I have a very long one page site. When I run the criticalcss grunt task, I get this error:

Running "criticalcss:home" (criticalcss) task Something went wrong with phantomjs... Fatal error: stdout maxBuffer exceeded.

When I run grunt -versions, I get: grunt-cli v0.1.13 grunt v0.4.2

npm is at v2.14.3

Anyone running into this issue or how I can fix it? It's driving me crazy right now ha.

Thanks guys!

jefflembeck commented 8 years ago

You should be able to fix this by increasing the buffer. You can do this by passing in a higher value for that option in the options hash.

On Tuesday, September 15, 2015, Grant Vinson notifications@github.com wrote:

I have been trying to figure this out all day and can't seem to pinpoint the issue. I have a very long one page site. When I run the criticalcss grunt task, I get this error:

— Reply to this email directly or view it on GitHub https://github.com/filamentgroup/grunt-criticalcss/issues/31.

jgillman commented 8 years ago

I'm running into the same issue and changing the buffer size doesn't seem to change anything. Is the buffer size in MB or KB?

I've got 8 GB of ram... should be plenty, right?

Whoops! Worked for me when I changed the buffer to 1000000*1024. It would be handy to know what those numbers are referencing. 1024 could be KB or MB (or even GB?).

johnbender commented 8 years ago

maxBuffer is in bytes, we should probably add that to the docs.

https://nodejs.org/api/child_process.html#child_process_child_process_execfile_file_args_options_callback