Free Support Forum -

Parser consuming not releasable memory


I found out that if Groupdocs.Parser tries to parse certain invalid PDF files and fails (expected), there remains allocated memory (of approx. file size + some percentage) which cannot be relased by calling Dispose() on parser, letting it out of scope etc. Also garbage collector does not pick it up.

Here is the download link for the file which can be reproducing above behavior, just create parser and try to extract text from it:


This issue is reproduced at our end. Hence, we’ve logged it in our internal issue tracking system with ID PARSERNET-1779. You’ll be notified in case of any further update.