I am running Aspose Imaging (Java version) as an AWS lambda task.In some cases a failure processing an unsupported or invalid image, causes a subsequent valid image to be processed incorrectly.
I believe that this might be caused by some leaks or by the cache … is it possible to force cache not to be used
(I don’t really need it anyway as I process a new image every time) so that every time I start processing an image, it is a brand new environment and there are no side effects from a previous failure?