not sure if this was triggered by wp-image-processing or one of it's dependencies though
not sure if this was triggered by wp-image-processing or one of it's dependencies though