Runnaway memory for specific images in converting HTML

pjb_maintology · October 1, 2020, 10:33am

Hi,
I have a scenario when certian images within the HTML are included the HTML to PDF conversion process goes into a runaway state consuming large amounts of memory very quickly (2Gb within 10s) and never completing. If the images are includde individually then the PDF generates OK.

Setup is:
.NET Core 3.1
Aspose.HTML v20.9

SampleProject.zip (41.3 KB)
VSScreenshot.jpg (19.5 KB)

We have a Aspose.Total for .NET licence and this issue occurs both with and without the licence. Using an older version of Aspose.HTML (19.8) the PDF generates but is currupted.

Thanks

asad.ali · October 1, 2020, 7:09pm

@pjb_maintology

We have tested the scenario in our environment and logged an issue as HTMLNET-2812 in our issue tracking system. We will further investigate it and keep you posted with the status of its rectification. Please be patient and spare us some time.

We are sorry for the inconvenience.

pjb_maintology · December 15, 2020, 9:34am

Hi, I see that the related issue HTMLNET-2812 has been closed. Please can you confirm the version that this fix is within?

aspose.notifier · December 16, 2020, 8:58pm

The issues you have found earlier (filed as HTMLNET-2812) have been fixed in this update.

David_jack · December 22, 2020, 6:28am

This Runaway memory for specific images in converting HTML is an issues id resolved by the update HTMLNET-2812 so please update this problem will be resolved,

asad.ali · December 22, 2020, 11:13pm

@David_jack

We are afraid that we could not understand exactly what you meant? The linked issue with this post has been resolved in Aspose.HTML for .NET 20.11. Are you still facing this issue?