It's specific to certain images. The issue is that we don't catch certain errors from
imagewebp
/
imagecreatefromwebp
and skip over these images. This particular error is a warning, but at least one seems to be a fatal error where our opportunities for error handling are limited. In the latter case I think we'll need to try to skip the image the next time optimization runs, but we can't avoid the process crashing
.