Memory leak when converting Office docs to PDF

Aspose.Total Product Family
21

Hi Reuben,


I’m glad to hear it did help. Yes, perhaps it should only be called after the memory increases to a certain level. Calling it with save might slowdown the process.

Please let me know if I can help with anything else.

Thanks,
22

HI, I have a similar experience with my application after processing a few hundred documents and converting them to PDF the memory grows exponentially. I did some monitoring and confirmed there were lots of objects being allocated to the LOH in memory, therefore not getting cleared when they should. Your documentation states that calling pdf.Save() should release the resources for Garbage collection, but that doesn’t seem to be the case. Can you provide some assistance? This is a production issue.

23

Hi Joe,

Can you please share which API are you using and also share your code?

Best Regards,