During construction of a PDF we are using a buffered image to fill an Image object
profileImage.getImageInfo().setSystemImage(bufImage);
Upon save we get the attached stack trace. This was working prior to upgrade to the newest 3.1 release. I have been successful in working around this issue by writing the image to a temp file (jpg) and changing the call to use the temp file.
ImageIO.write(bufImage, “jpg”, tempFile);
profileImage.getImageInfo().setImageStream(new FileInputStream(tempFile));
As an additional bit of information, attempting to use png as the file format for the creation of the temp file occasionally yields out of memory issues on the save call as the save somehow eats up all available memory allocated to the JVM (tried it with up to 8G).
STACK TRACE attached.
Hello Steve,
Thanks for using our products.
I am testing this scenario in my environment and will get back to you soon. We are sorry for this inconvenience.
Hi Steve,
Thanks for your patience.
I have tested the scenario and I am able to reproduce the same problem. For the sake of correction, I have logged it in our issue tracking system as PDFJAVA-33135. We will investigate this issue in details and will keep you updated on the status of a correction.
We apologize for your inconvenience.
The issues you have found earlier (filed as PDFJAVA-33135) have been fixed in Aspose.Pdf for Java 3.2.0.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.