Our immediate goal is to find an API for Office or OpenOffice documents to PDF conversion, Office and PDF formats processing and PDF to EPUB conversion.
Currently we have encountered an out of memory error with the PDF to EPUB conversion.
The issue at hand concerns a PDF file of about 500 pages and 33 Mb. The test program runs with VM parameters -Xmx1350m.
The PDF is loaded rather quickly, the the exception occurs some 20 minutes later.
We can provide the sample file if needed.
Below are the Java code (fairly simple) and the fired exception.
Thank you for help.
System.out.println("loading test2.pdf");
com.aspose.pdf.Document pdfDocument = new com.aspose.pdf.Document("test2.pdf");`
System.out.println("test2.pdf loaded");
com.aspose.pdf.EpubSaveOptions options = new com.aspose.pdf.EpubSaveOptions(); options.ContentRecognitionMode = com.aspose.pdf.EpubSaveOptions.RecognitionMode.Flow;
System.out.println("saving test2.epub");
pdfDocument.save("test2_pdf_out.epub", options);
System.out.println("test2.epub saved");
loading test2.pdf
test2.pdf loaded
saving test2.epub
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at com.aspose.pdf.internal.p801.z177.<init>(Unknown Source)
at com.aspose.pdf.internal.p801.z177.m13(Unknown Source)
at com.aspose.pdf.internal.p165.z28.m1(Unknown Source)
at com.aspose.pdf.internal.p165.z28.m1(Unknown Source)
at com.aspose.pdf.internal.p165.z28.m1(Unknown Source)
at com.aspose.pdf.internal.p166.z1.m1(Unknown Source)
at com.aspose.pdf.internal.p166.z1.m1(Unknown Source)
at com.aspose.pdf.internal.p166.z1.m1(Unknown Source)
at com.aspose.pdf.internal.p165.z3.m1(Unknown Source)
at com.aspose.pdf.internal.p4.z9.m1(Unknown Source)
at com.aspose.pdf.internal.p4.z9.m1(Unknown Source)
at com.aspose.pdf.internal.p161.z1.m1(Unknown Source)
at com.aspose.pdf.z67.m1(Unknown Source)
at com.aspose.pdf.ADocument.m1(Unknown Source)
at com.aspose.pdf.Document.m1(Unknown Source)
at com.aspose.pdf.ADocument.save(Unknown Source)
at com.aspose.pdf.Document.save(Unknown Source)
at test.Aspose.main(Aspose.java:44)
Please upload your sample PDF document to some public file sharer (e.g Dropbox or Google Drive) and share the link here. We will test the scenario in our environment and address it accordingly. Also, we will really appreciate if you can please share the OS and JDK version, in which your program is running.
We were managed to replicate the issue in our environment and for the sake of correction, we have logged it as PDFJAVA-37419 in our issue tracking system. We will further investigate it in details and keep you informed with the status of its correction. Please be patient and spare us little time.
As we have recently logged the issue in our bug tracking system, so I am afraid that it is pending for investigation. Product team will surely plan to start investigation against logged ticket, as per their development schedule. We will inform you in case we have some definite updates in this regard. Please spare us little time.
We are sorry for the inconvenience.
PS: Please try increasing memory by specifying Xmx parameter, and let us know about the results.
The product team has investigated earlier logged issue PDFJAVA-37419 and as per their investigation, your PDF document has many images and in process of conversion these images are decompressed to bitmap data - which needs at least 2.2GB of memory. So, please, use VM parameters:
-Xmx2300m
Please, note that there is also some problem with image color space in this document that leads to losing all images. For fixing the bug an issue PDFJAVA-37455 has been created in our issue tracking system. We will let you know once we have some definite updates regarding its rectification. Please spare us little time.
Thanks for the reply, but you haven’t been paying attention to my problem : I’m running 32 bit VM, thus reserving 2.3 Gb of heap space is not possible.
We apologize that we missed these details while suggesting you the solution of the issue, we have re-opened the logged issue and shared your concerns with respective team. As soon as we receive so feedback against updated details of the issue, we will let you know. Please spare us little time.
Please note that we have already started investigation of earlier logged issues and as per results of the initial investigation, the issues are blocked by some pending internal changes in the API. Please also note that these issues have been logged under normal/free support model where issues are being resolved on first come first serve basis.
There are other pending issues in the queue as well, which were logged prior to your issues and we apologize that we are not in position to share any reliable ETA for now. However, we will definitely provide fix against your issues after resolving previously logged issues.
Furthermore, we also offer Paid Support model to our customers who want their issues fixed on urgent basis. The issues logged under Paid Support model, have precedence over the issues logged under free support mode. Though Paid Support model does not guarantee any immediate solutions but it does expedite the resolution process. For more information you may please visit Paid Support FAQ.
Concerning to the logged issues, we will definitely inform you as soon as we have some definite updates regarding their resolution progress. Please be patient and spare us little time.
I understand that there is also paid support, but you seem to miss the fact that I am a POTENTIAL CUSTOMER (see my first post) that now has very SERIOUS DOUBTS about the reliability of your product.
This issue was opened 5 MONTH AGO; last reply was 3 MONTH AGO.
Please note that every logged issue is significant for us and draws equal attention. However, logged issues have been resolved on first come first serve basis, which we believe is the fairest policy to everyone. We will definitely provide fix against your logged issues, after resolving previously logged ones. We have recorded your concerns and will surely consider them while investigating the issue. We appreciate your patience and comprehension in this regard. Please spare us little time.
The issues you have found earlier (filed as ) have been fixed in this update. This message was posted using BugNotificationTool from Downloads module by MuzammilKhan