thanks for the quick reply!
Could you please specify what do you mean exactly by “shared application” ?
I’m calling conversions in a consequent manner, one after another, each conversion cycle has dedicated initialization and disposal of the required Aspose API objects (the “using” sections in the ConvertMht() method), so I expect that these resources are disposed of properly after each conversion. Instead I observe that the memory is piled up and not released by Aspose.Html. If you run the app using VS menu Debug -> Performance Profiler, and make a couple of screenshots, you may observe the objects held, e.g.
image.png (6.7 KB)
And after all 100 conversions have completed and a Garbage Collection is forced for several times, the memory held is still above 1 GB.
Our app uses Aspose to convert thousands of thousands of files literally, so performance and memory usage/allocation means a lot to us.
Please, let me know if we miss here anything important, but I can tell you that I’ve run dozens of similar tests for other file formats and it’s only the MHT that breaks that wild.