NOTE: issue found only in .NET Framework (4.8 in our case), not in .NET Core.
We run a high volume HTML to PDF conversion on Azure App Services. HTML frequently contains images. When we migrated from a different vendor to Aspose, we began to experience rapid increase in memory usage, leading to eventual slowdowns and even complete lack of response from the app service, until forced restarts. Analyzing memory dumps showed the the memory is tied in Large Object Heap, further investigation indicated that memory is being mostly used by image sizing functions of System.Drawing namespace, called by Aspose.
We worked around the issue in one of our environments by moving the conversion method to a .NET Core Azure function, where the issue doesn’t seem to appear. Unfortunately, in a different version of our product this is not an option.
We need you guys to investigate and fix the issue, as it prevents us from using your product fully. We prefer to use the same component in all our environments, as for now we are forced to still use one of your competitors’ components.