memory leak problem with your PDF to Image Converter SDK


We have encountered a significant memory leak with your SDK.  Please let us know if this is something you can fix (and if so, when) – if not then we will have to design around it.


The Memory leak issue

The virtual memory size information available in the windows task manager is used to check for a possible memory leak.

Two test functions were used:

1. RasterizeNoThread()
This function is a loop that calls PDFToImageConverter function repeatedly. Monitoring the PVM shows no increase in the VM size.

2. Rasterize()
This function uses the _beginthread function. Monitoring the PVM shows a continuous increase in the VM size after the application has allocated all the memory it needs. This indicates a memory leak.

I have attached a PDF file in addition to test functions.
We haven't a new version of PDF2Image SDK product at the moment, we will try to solve this problem in the future releases, at the moment, we suggest you may by following steps to solve this memory leak problem,

1. You can write a standalone EXE Command Line application to call the PDF2Image SDK to convert PDF files to Image files,
2. Call this Command Line EXE application from your main application,
3. OK.

Because EXE process will release its memory after it exit from Windows, so this solution will solve the memory leak problem completely, we hoping this solution will useful to you.

VN:F [1.9.20_1166]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.20_1166]
Rating: 0 (from 0 votes)

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *

Verify Code   If you cannot see the CheckCode image,please refresh the page again!