Dear，
The aspose-pdf component used in production has been found to have a memory leak
Troubleshooting Procedure: No service interface is used to convert PDFS to pictures on weekends, and no aspose is used in the background. About 2 GB of cache is stored in the dumped memory
The code uses the aspose component in the following way. After converting pdf to jpg/ single-page pdf, the close() method is manually executed. Would you like to ask whether the use is wrong, resulting in memory leakage?
The Aspose-pdf version is as follows
com.aspose
aspose-pdf
< version > 20.6 < / version >
image.png (95.3 KB)
@Maggie_Pan
Document.Close() method cannot be a culprit for memory leak. However, we request you please try with 24.1 version of the API that has a lot of improvements in terms of memory consumptions. Please try to use it and let us know if issue keeps persisting by sharing some sample document and screenshots of the logs you are generating. We will further proceed to assist you accordingly.
Dear:
When we use the 24.1 version with your proposed solution, the program is allowed to encounter the following error message, how to deal with it? Are there any alternative solutions?
The subscription included in this license allows free upgrades until 11 Sep 2020, but this version of the product was released on 29 Oct 2023. Please renew the subscription or use a previous version of the product.
@Maggie_Pan
Are you saying that 24.1 version is able to resolve the issue you were facing? Have you tried testing with it using a free 30-days temporary license?