[Poppler-bugs] [Bug 20148] New: pdftotext memory leak?

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Feb 16 14:27:10 PST 2009


http://bugs.freedesktop.org/show_bug.cgi?id=20148

           Summary: pdftotext memory leak?
           Product: poppler
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
        AssignedTo: poppler-bugs at lists.freedesktop.org
        ReportedBy: debian at oursours.net


Created an attachment (id=23002)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=23002)
valgrind --leak-check=full -v --show-reachable=yes pdftotext -enc UTF-8
-nopgbrk WSGI_final.pdf

Hi,

I'm trying to use poppler as a library. I've taken the code from pdftotext.cc
and replaced FileStreams with MemStreams.

I face memory leaks so I'm trying to trace it down.

Just running valgrind onto the original "pdftotext" utility shows 28 KB is
lost, whatever the size of the PDF file.

I'd like to understand if it's a problem in poppler or if the pdftotext source
code is just not a reference and lacks some clean up code. As this is my source
of inspiration, I rely on it to learn how to use poppler.

I'm attaching valgrind output.

I really can't choose the bugzilla component by myself. I hardly know if
"pdftotext" is based on bare poppler or the glib wrapper.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the Poppler-bugs mailing list