andrews05

Hi @guilhermesimoes Sorry to hear this Is happening. How much memory and how many cpu cores do you have? You should be able to work around the issue by capping...

Oxipng doesn't currently have any constraints on memory usage (see #411). But more threads = more memory, so you can still exert some control over memory by capping the threads...

Closing this for now as we've made some improvements in v9.1.5 to reduce memory usage. Beyond that it's up to the user to employ flags like `--threads` or `--sequential` when...

As much as I would love to see Chrome forced to implement JPEG XL, I'm afraid these comments making "demands" are based on a misunderstanding of who and what Interop...

Gracefully handling the situation is unfortunately a pretty difficult problem. Knowing how much memory you need up front is not really feasible if you're processing a big queue of files...

@jonnyawsom3 I'm not quite sure what you're suggesting, would you be able to clarify? Single filter strategies are of course always possible by just selecting one filter as you show....

These are all good thoughts guys but I'm afraid I still have big concerns about feasibility, effectiveness, and complexity of any such thing. This is not something I intend to...

As a long-form option, it should retain some degree of clarity about the meaning. I realise we have a number of options already which *don't* (such as --nx, --nz etc)...

@ace-dent If you're just doing one file at a time then you don't need to use this parameter. I'm not sure what you mean about it not being an option?

Thanks for the input everyone, we settled on `--sequential`.