Ubuntu
evince package

evince causes high X load while searching

Bug #132556 reported by apm
2
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evince

While using the search function in evince to search through PDFs, the CPU usage of X is very high.

This is on evince 0.9.3 from recent gutsy.

Using the vesa driver of Xorg, X uses up about 70% of CPU and evince 30% while searching the PDF.

Presumable due to a separate bug that makes the open source ati driver (radeon 9600 mobile card) slower than the vesa driver, the CPU split while search in evince is even worse with X using up more than 90% of CPU. This also causes the search to be much slower than with the vesa driver.

Expected behaviour: Evince should not cause significant load on the X server while simply searching through a document.

Should you need any further information to help resolve this issue, I am happy to provide it.

Thanks

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. Could be a duplicate of bug #122786

Changed in evince:
assignee: nobody → desktop-bugs
importance: Undecided → Low
Revision history for this message
apm (awp-monkey) wrote :

I am not sure if this is a duplicate of bug #122786. The (separate) issue with the radeon driver may very well be that bug (so thanks for pointing this out and I will have a look), but I think it remains the question why is evince putting so much load on the xserver during searching (in which graphically nothing but the progress count changes) to trigger this graphics bug and slow down the search it self?

(The rest of this comment is pure speculation so most likely wrong)
Could it be, that something during search is constantly causing a redraw of too much of the screen? In an attempt of profiling the problem, one of the highest ranking functions in evince was ev_view_expose_event. Although the actual time was somewhere in the sub permil range, so could very well be noise. Most time was spent in libfb.so (when using the radeon driver). Also I didn't have the debug symbols of poppler, as there doesn't seem to be a dbg package of it in the gutsy repository.

thanks for looking into this

Revision history for this message
Sebastien Bacher (seb128) wrote :

There is a dbgsym package for everything in the archive, you can read http://wiki.ubuntu.com/DebuggingProgramCrash on how to install those

The slowness is likely due to cairo hitting a slow codepath in the driver

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you with Hardy? Thanks in advance.

Changed in evince:
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to 'New'. Thanks again!

Changed in evince:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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