ArgumentOutOfRangeException exception when using IsLowMemoryMode

We just purchased Aspose for the purpose of converting to PDF/A-compliant PDFs. However, when converting some v1.6 PDFs, we get the following error.

ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

If I turn of PdfFormatConversionOptions.IsLowMemoryMode the conversion is successful. I’ve created a test app to reproduce the issue, which I can provide.

@cgillett

Thank you for contacting support.

Would you please share a narrowed down sample application reproducing this issue so that we may try to reproduce and investigate it in our environment.

AsposePdfAConversionIssue.zip (274.2 KB)
The sample app is attached. Nuget packages (for the Aspose.PDF reference) will need to be restored before running the project.

@cgillett

We have worked with the data shared by you and have been able to reproduce the issue in our environment. A ticket with ID PDFNET-45466 has been logged in our issue management system for further investigation and resolution. The ticket ID has been linked with this thread so that you will receive notification as soon as the ticket is resolved.

We are sorry for the inconvenience.

Thank you for the update.

Do you know roughly how long the resolution will take? We have customers waiting on this particular feature.

@cgillett

The ticket has just been logged in our issue management system and is pending for investigations. It will be scheduled on its due turn which can take some months owing to previously logged tickets. We appreciate your patience and comprehension in this regard.

However, we also offer Paid Support, where issues are used to be investigated with higher priority. Our customers, who have paid support subscription, report their issue there which are meant to be investigated urgently. In case your reported issue is a blocker, you may please consider subscribing for Paid Support. For further information, please visit Paid Support FAQs.

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