During the process of converting a 4 MB PDF containing 15 pages to TIFF format using my API, it appears that a significant amount of memory was consumed, with a total usage of 1.1 GB. Despite disposing of all resources, the container continued to utilize around 500MB in the background. Upon further investigation, it became clear that there was a memory leakage issue, which surfaced after repeated attempts to execute the same routine. Is there any solution to optimize memory usage?
Would you kindly share your sample PDF file along with the code snippet and docker file for our reference? We will test the scenario in our environment and address it accordingly.
I will prepare separate version for testing soon.
Sure, please take your time and share the requested information with us. We will further proceed to assist you accordingly.
Aspose-TestTiffConverter_windows.zip (1.1 MB)
Aspose-TestTiffConverterLinux.zip (1.1 MB)
And additionally I executed 3 times same requests( look into archives) on both environments for same file from archive and received huge usage of memory in both cases for converting of 1.1 MB pdf file to TIFF (15 pages). And additionally after last GC run, API were still using 400-500 MB of memory for doing nothing. Could you help me with pieces of advise regarding optimization or fixing?
Linux
Windows
An issue as PDFNET-54018 has been logged in our issue tracking system to further analyze this case. We will look into its details and keep you posted with the status of its correction. Please be patient and spare us some time.
We are sorry for the inconvenience.