Aspose.Pdf for .NET PDF/A 1B conversion High memory consumption / OutOfMemoryException / Very Slow

We are currently using Aspose in Production and noticed very high memory consumption when concatenating 2 rather medium sized PDF’s and then execute a PDF/A 1b conversion on the merged PDF.



We are event getting an OutOfMemory exception on the Save operation after the conversion has happened at around 1.6 GB memory consumption of the test console app (see attached file)



We can get rid of that OutOfMemoryException by running the console app in 64bit mode. But you can notice extremely high memory consumption during the conversion up to 6 GB and more for those 2 tiny pdf’s. And it takes ages to complete.



Can you give me some advice? What are we doing wrong? Is that a known Issue with your PDF library?



I am running it on the following specs:

CPU: Intel Xeon E7-4860 v2

RAM: 12 GB

Operating System: Windows Server 2012 R2 64-bit

Hi Tim,


Thanks
for using our API’s.
<o:p></o:p>

I
have tested the scenario and I am able to notice the same problem. For the sake
of correction, I have logged this problem as PDFNEWNET-40464 in
our issue tracking system. We will further look into the details of this
problem and will keep you updated on the status of correction. Please be
patient and spare us little time. We are sorry for this inconvenience.

The issues you have found earlier (filed as PDFNET-40464) have been fixed in Aspose.PDF for .NET 23.8.