memory leak in evince: using gigabytes of ram when selecting text

Bug #1287124 reported by sachit
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

When I select text in a certain pdf, evince consumes hundreds of MBs to a few GBs of RAM. This ram is not freed on deselection. High CPU usage accompanies the RAM allocation.

version: evince 3.4.0
OS: ubuntu 12.04 fully updated.

Steps to reproduce: Open the pdf I have attached and attempt to select around a page of text. Keep a system monitor or a terminal open so you can kill it easily if your system freezes for lack of RAM.

Revision history for this message
sachit (staticd-growthecommons) wrote :
Revision history for this message
Quinn Balazs (qbalazs) wrote :

Please collect and attach Valgrind forensics using the method detailed here: https://wiki.ubuntu.com/Valgrind. These will allow us to see specifically what the issue is. Before being able to collect Valgrind forensics you will need to install the debug symbols for evince if you don't currently have those installed (sudo apt-get install evince-dbg).

Once you've done that, set the status here back to new, and we'll take a look at the logs.

Thanks.

Changed in evince (Ubuntu):
status: New → Incomplete
Revision history for this message
sachit (staticd-growthecommons) wrote :

The valgrind log of he operation after normal termination.

Quinn Balazs (qbalazs)
Changed in evince (Ubuntu):
status: Incomplete → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in evince (Ubuntu):
status: New → Confirmed
Revision history for this message
Glenn Horton-Smith (glenn-hortonsmith) wrote :

I can confirm I see the same behavior with the pdf file provided by the original reporter.

The valgrind output may be difficult to interpret. I see many of the same errors in valgrind of evince processing pdf files that don't provoke this behavior. I found it hard to find any error that wasn't present in both cases.

Revision history for this message
penalvch (penalvch) wrote :

sachit, thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Vivid Vervet.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

Changed in evince (Ubuntu):
importance: Undecided → Low
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.