Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#29086 - zathura+pdf: excessive memory usage (memory leak?)

Attached to Project: Community Packages
Opened by Alex (bsdard) - Saturday, 24 March 2012, 00:18 GMT
Last edited by Jelle van der Waa (jelly) - Saturday, 24 March 2012, 09:01 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After installing the latest zathura/zathura-pdf-plugin I noticed that it started to hang after continuous usage. I started monitoring memory, and noticed that VIRT/RES increases grows to a 400MB+ when looking through big pdf documents (eg. 900page ebook). Memory grows with every new page displayed, so I suppose there is a nasty memory leak or architectural deficiency in the new version.

For comparison, I've compiled the good old 0.8.5 and the RES usag was at about 39M-50M constantly.

Additional info:
* package version(s)
zathura - 0.1.1-4 (x686)
zathura-pdf-poppler-0.1.1-1 (x686)
* config and/or log files etc.
N/A

Steps to reproduce:
1. install zathura and zathura-pdf-poppler
2. run top -p `pidof zathura` in terminal.
3. open a big pdf document and scroll down. Not necessarily fast, just page by page normally.
4. observe VIRT/RES grow with every page indefinitely.

I had it grown to 400Mb+ after I scrolled about 25-30% of the book. I would expect it would eat about 1.5Gb by the end of the book.

The issue is not reproducible with the old Zathura (0.8.5 tested).

Can old zathura remain in the package repository before the new one is fixed and stable? Can the new version be removed as it may affect system stability?

I've deinstalled the packages and currently running the compiled old version.
This task depends upon

Closed by  Jelle van der Waa (jelly)
Saturday, 24 March 2012, 09:01 GMT
Reason for closing:  Upstream
Additional comments about closing:  upstream bug should go upstream. So Thanks for reporting it there
Comment by Alex (bsdard) - Saturday, 24 March 2012, 08:35 GMT
reported a bug ID0000159 on the pwmt.org (http://bt.pwmt.org/view.php?id=159)

Loading...