This bug was fixed in the package python-poppler - 0.12.1-8
---
python-poppler (0.12.1-8) unstable; urgency=low
* uploading to unstable
-- Andrea Gasparini ga...@yattaweb.it Sun, 29 Apr 2012 17:51:08
+0200
** Changed in: python-poppler (Ubuntu)
Status: Triaged = Fix
** Branch linked: lp:debian/experimental/python-poppler
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/316722
Title:
python-poppler doesn't close files
To manage notifications about this bug go to:
Are there any objections to the solution proposed in comment #7? I can
confirm that the patch from comment #8 solves all memleaks that I have
encountered (see bug #509408). Who is responsible for accepting and
applying this patch into the upstream project?
--
You received this bug notification
** Changed in: python-poppler (Ubuntu)
Status: New = Triaged
--
python-poppler doesn't close files
https://bugs.launchpad.net/bugs/316722
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I just compiled the latest python-poppler revision including the
solution presented by BenjaminBerg (Thanks!) and can confirm it is
working. Both my own application and the demo program in the bug
description show no increased memory usage and the proc/{id}/fd folder
shows the objects are
** Tags added: patch
--
python-poppler doesn't close files
https://bugs.launchpad.net/bugs/316722
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Ehm? Why is a patch to poppler needed in any way?
(this is also basically the same as #509408, but that is known ...)
As far as I can tell the only issue is that poppler-python is missing the
(caller-owns-return #t)
all over the place in the poppler.defs file. This means that while the python
** Changed in: poppler-python
Importance: Undecided = Medium
** Changed in: poppler-python
Milestone: None = development
--
python-poppler doesn't close files
https://bugs.launchpad.net/bugs/316722
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm still waiting for my patch to be pushed into poppler itself, let's
cross fingers :)
** Changed in: poppler-python
Status: New = In Progress
** Changed in: poppler-python
Assignee: (unassigned) = Gian Mario Tagliaretti (gianmt)
--
python-poppler doesn't close files
how did you measure the leaks?
Leave it running for a few minutes while looking at gnome-system-monitor
--
python-poppler doesn't close files
https://bugs.launchpad.net/bugs/316722
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I have files a bug with a patch that adds a poppler.Document.release()
that will solve this issue, hopefully it will get in poppler-0.12,
valgrind shows no complaints
==6750== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1248 from 9)
==6750== malloc/free: in use at exit: 3,470,220 bytes
I did investigate further and did some testing:
Current release:
- all python objects get destroyed automatically
- files stay open
- memory leak per document_new_from_file(): 40 kB (for a 300 kB pdf file)
- gc.collect() does nothing
If you call g_object_unref(hash(doc)) after each call to
I've looking into this one for a long time with no real solution but I
feel the GC could be the one to blame, did you investigate further?
--
python-poppler doesn't close files
https://bugs.launchpad.net/bugs/316722
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: python-poppler (Ubuntu)
Importance: Undecided
Status: New
--
python-poppler doesn't close files
https://bugs.launchpad.net/bugs/316722
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
14 matches
Mail list logo
