We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Document.Optimize corrupts pdf document

Hello,


We’re using the Aspose.Pdf package v17.4.0 for .Net.
We’ve noticed that calling Optimize() on a specific pdf document causes it to become corrupted when saved to an output file (all the pages are blank when opened in Adobe Acrobat).
Currently, we’ve only seen it happen with this one document, so not sure what is going wrong.

Here’s some simple sample code:
Document doc = new Document(inputFile);
doc.Optimize();
doc.Save(outputFile);

If we remove the Optimize call, then the output is fine.
I’ve attached the document we’re seeing this with (InputDoc.pdf), and the corrupted output (OutputDoc.pdf).
Any help would be appreciated.

Thanks,
Luke

Hi Luke,


Thanks for contacting support.

I have tested the scenario in our environment and have managed to reproduce the issue which you have reported. For the sake of investigation, I have logged it as PDFNET-42749 in our issue tracking system. We will further look into the details of the issue and keep you informed with the status of its rectification. Please be patient and spare us little time.

We are sorry for the inconvenience.


Best Regards,

Hello,


Has there been any progress on this issue?

Thanks.

Hi Luke,


Thanks for your inquiry.

As we have recently notified the development team about the issue, so I am afraid that it is still pending for review, as there are other pending issues in the queue as well and relevant team has been busy in reviewing them. As soon as we have some definite updates regarding resolution of your issue, we will certainly let you know. Please be patient and spare us little time.

We are sorry for the inconvenience.


Best Regards,

Hello,

My name is Casimir Simpson from Citrix Sharefile and one of Luke’s colleagues. I’m sending this email for an update on this ticket.

@Casimirs,

Thanks for contacting support.

I am afraid the earlier reported issue is pending for review and is not yet resolved. However the product team will surely consider evaluating it as per their development schedule and as soon as we have some definite updates, we will let you know. Please be patient and spare us little time. Your patience and comprehension is greatly appreciated in this regard.

Regards,
Nayyer Shahbaz

Hello, I seem to be experiencing this issue also with Aspose.pdf for Java (19.3). I know you have been working for a solution for .net since(or you have an open ticket to work on a solution), can we expect also a solution for java, and if yes is it likely to be soon ?

Thanks

@yomeJean

We apologize for the inconvenience.

The issue has already been logged for .NET API and is pending for resolution due to other high priority implementations and enhancements. Furthermore, once the issue is resolved in Aspose.PDF for .NET, its fix will also be ported in equivalent version of Java API. As soon as the issue is resolved or we have any update in this regard, we will share with you.