Memory leak in Aspose.Pdf

Hi,

We just purchased the latest Aspose.Total for our company due to an issue we expirienced with version 16. The issue was resolved but the new version 19.6 is failing existing unit test that worked fine with the previous version.

When running png -> pdf conversion from inside a unit test in a loop program consumes excessive memory and crashes with OutOfMemory exception. When the same code is executed from Console application memory remains constant and program completes without errors.

Please help otherwise we can’t integrate with version 19.6 we just bought.

@CorvelAspose

Thank you for contacting support.

Please note that support is provided based on latest available version so please try using Aspose.PDF for .NET 19.10. If the issue persists then please share sample application containing SSCCE code along with necessary required files, if any. So that we may try to reproduce and investigate it in our environment.

The latest version has the same problem:

Please see the linked zip that includes the solution demonstrating the problem. The solution contains 2 projects: Aspose16Test & Aspose19Test. Both projects are console applications trying to convert the same png file 1,000 times. Both apps complete without errors when executed as console apps. When the same method is executed as unit test under Visual Studio Aspose16Test still succeeds but Aspose19Test starts consuming large amounts of memory and crashes within a minute. Both apps load test png file in memory once and write output pdf file into the same MemoryStream that gets reset after each iteration so no other I/O activity is going on.

@CorvelAspose

Thank you for elaborating further.

We have logged a ticket with ID PDFNET-47172 in our issue management system for further investigations. We will let you know once any update will be available in this regard.

Do you have an approximate time line for the fix? As it stands now we can’t use the latest version in our system as it might crash the parent process it is invoked from.

@CorvelAspose

We have recorded the request for ETA and will let you know once it will be available.