Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
poppler
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 613
    • Issues 613
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 40
    • Merge Requests 40
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • poppler
  • poppler
  • Issues
  • #569

Closed
Open
Opened Oct 07, 2014 by Bugzilla Migration User@bugzilla-migration

Memory leak (reloading the same file increases memory consumption)

Submitted by Phillip Berndt

Assigned to poppler-bugs

Link to original bug (#84737)

Description

Created attachment 107455 Test program

The attached test program loads a PDF file, draws it, unloads the file, and then starts over again. To compile it, use

cc test.c -o test $(pkg-config --libs --cflags gtk+-3.0 glib-2.0 cairo gio-2.0 poppler-glib)

and then start it with a PDF file as its first argument, preferably a large one, like a paper or a book.

I'd expect some, limited growth in memory consumption, due to things like caching, but instead memory usage appears to grow linearly. With a 147kB PDF, I'm at 1.5GB memory consumption after some minutes. I tested this with Poppler 0.24.5 and 0.26.5, but not with the latest git version, on a machine running Ubuntu Trusty.

If I run the same program with a gdk-pixbuf and images instead of poppler, memory consumption does not increase, so I am quite positive that this is indeed a poppler bug and not one in gtk/glib. I did not make any attempts to find the source within poppler though, so I can't tell if this really is a problem in the glib frontend or if the problem lies in the backend.

Attachment 107455, "Test program":
test.c

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: poppler/poppler#569