Problem with Some PCL Files


#1

We have a process that converts PCL files to PDF files. Some PCL files process fine. Other files, (which are viewable in other tools) cause the program to end immediately. The Catch block does not get to run. In the debugger the message appearing before termination is:

Your app has entered a break state, but there is no code to show because all threads were executing external code (typically system or framework code).
System.NullReferenceException: ‘Object reference not set to an instance of an object.’

We are running Aspose.PDF version 19.6.0.0.

Is this a known issue? Is there any advice on:
A. Catching the error
B. Working around the error

Aspose.Pdf.Facades.PdfPageEditor pEdit = new Aspose.Pdf.Facades.PdfPageEditor();
Aspose.Pdf.Facades.PdfConverter pdfConverter = new Aspose.Pdf.Facades.PdfConverter();
Aspose.Pdf.LoadOptions loadopt = new Aspose.Pdf.PclLoadOptions();
foreach (string file in fileWithPathArray)
{
    Aspose.Pdf.Document doc;
    try
    {
        // Crashes on the following:
        doc = new Aspose.Pdf.Document(file, loadopt);
    }
    catch (System.Exception ex)
    {
        // Never gets this far
        throw ex;
    }

#2

@varsoil

Thank you for contacting support.

Would you please share complete stack trace of exception along with source and generated files as ZIP archives, so that we may try to reproduce and investigate it in our environment.


#3

Sending zip with code, input PCL file, and stack trace. Binaries removed to meet max-size limit.

It may be that the source system is producing PCL files with formatting issues. These problems are ignored by the other conversion package of which we are trying to replace with Aspose.pdf.

(Correcting the PCL generator is not a near-term option, due to the volume of that change.)

I would like the file to be converted if at all possible, but in the least, I need to be able to catch any error (rather than have it crash.) Thanks.
Code198954.zip (396.1 KB)


#4

@varsoil

Thank you for sharing requested data.

We have worked with the data and have been able to reproduce the issue in our environment. A ticket with ID PDFNET-46609 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.


#5

Thanks.
I can wait for a resolution or I can begin searching for an alternative means of working with the files. Do you have a general sense of how long it should be for a resolution to be available? One month? Six months? Longer?


#6

@varsoil

Please note that the ticket has been logged under free support model and will be investigated on first come first serve basis. Therefore, it may take some months to resolve. As soon as we have some definite updates or ETA regarding ticket resolution, we will let you know.

Moreover, 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.