Memory Leak while PDF to HTML & HTML to PDF Conversion - .NET

Aspose.PDF Product Family
1
  • We found very strange issue while converting PDF to HTML & HTML to PDF in our .NET Application.
  • Memory usage going out of memory everyday over multiple transactions (100%).
  • It is really bizarre issue (Memory Leak) and we don’t have any solution other than restarting the server

Please look into it ASAP and revert back to us.

ASPOSE.PDF version is: 21.10.0.0
ASPOSE.HTML version is: 21.11.0.0

We found similar kind of ticket which has been raised on aspose forum:

Thanks,
Saleem Shaikh.

2

@saleemshaikh

Please use the latest version of Aspose.PDF for .NET 22.5 and Aspose.HTML for .NET 22.5 and let us know how it goes on your side.

If you still face problem, please attach the following resources here for testing:

  • Your input files.
  • Please create a standalone console application (source code without compilation errors) that helps us to reproduce your problem on our end and attach it here for testing.

As soon as you get these pieces of information ready, we will start investigation into your issue and provide you more information. Thanks for your cooperation.

PS: To attach these resources, please zip and upload them.

3

@tahir.manzoor

Thanks for your response.

We have upgraded the version for both the license to 22.5 but the memory consumption error is still there.

It will not work with Console Application to reproduce the issue, as the issue is related to the web application.

We observed while the conversion of documents, Application Pool is increasing gradually which is exceeding the total limit.

Almost after 20 to 30 operations, this is happening.

Please help us to resolve this issue as it’s resulting site down.

Thanks

4

@saleemshaikh

Thanks for sharing the detail. Please share the simple web application along with your web server detail. We will investigate the same scenario at our end and provide you more information on it.

It would be great if you please share the complete steps that you are following to reproduce the same issue. Thanks for your cooperation.