Fails when processing very large folders about grunt-imageoptim HOT 15 CLOSED

Sorry for the delay getting to this, I've been really busy the last few weeks with my regular work.

I take it from your description that the CLI runs for quite a long time, chugging through all the files - then after quite some time falls over? Does it always fail at the end while it's writing out the summary of savings? or sometimes before then?

If the former, I wonder if the summary output is so large it occupies more memory than is available to the process. If the latter, I'll need to think about it some more :)

from grunt-imageoptim.

No need to apologize :)

The CLI does indeed run for a long time chugging through the files. Basically the CLI opens the ImageOptim GUI, which runs for ages while the CLI just idles. Then, once the GUI completes its optimizations, the CLI starts writing the summary. It's during this that it dies. So far it's never died before writing a big chunk of the summary -- as I said above, somewhere around 1000 files is typical.

Thanks!

from grunt-imageoptim.

Great, if it wasn't that I would have been short of ideas. I think the buffer of text being prepared for writing out to the terminal is so big that the process runs out of memory.

Thanks pal.

from grunt-imageoptim.

Ok cool. I'll try freeing up some memory and re-running to see if that helps.

from grunt-imageoptim.

I don't think that will help, I need to change the CLI.

from grunt-imageoptim.

I'm having the exact same thing happen as described by @nwtn here.

from grunt-imageoptim.

Thanks @curtisblackwell, @nwtn — I will address this soon.

from grunt-imageoptim.

Any update on this bug? Unfortunately, I've got the same problem and need to split my files in separate runs to have them optimised.

from grunt-imageoptim.

Is it possible this could be fixed by not outputting the savings for each file? A total or per-directory savings would be enough for me.

from grunt-imageoptim.

@curtisblackwell @schiggi @nwtn

Just a note to assure you I'm aware of the issue. The long delays are down to contract and freelance work (I'm even working at the moment) but I intend to write a fix as soon as I have enough time.

from grunt-imageoptim.

@JamieMason do you know what the cause of the problem is? I'm going to take a look at this this week and will submit a PR, but if you know where I should focus my attention, that would be super helpful.

from grunt-imageoptim.

Workaround posted in commits/PRs above. @JamieMason it would be awesome if you could take a look.

@curtisblackwell @schiggi @intellix hopefully this solves your problems too.

from grunt-imageoptim.

Hugely grateful for this @nwtn. I've been swamped with client work for quite some time but promise to pick this and other issues up asap. Thanks again for your help and patience.

from grunt-imageoptim.

@JamieMason no worries, I know how things can get :D

from grunt-imageoptim.

Sorry for the huge wait, I will close this and instead track ongoing issues over at https://github.com/JamieMason/ImageOptim-CLI/.

from grunt-imageoptim.