GNOME Bugzilla – Bug 453123
very hi cpu usage when scrolling pdf
Last modified: 2007-08-24 09:21:43 UTC
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/evince/+bug/122786 and sent on https://bugs.freedesktop.org/show_bug.cgi?id=11438 "Binary package hint: evince I'm using gutsy, and I have evince 0.9.1-0ubuntu1. I notice a very hi cpu usage in this version of evince. When scrolling, and when moving a small window (for instance a terminal) over evince with a open pdf. This makes evince bad because it is too slow to use! ... http://launchpadlibrarian.net/8228961/01%20-%20IntroCorsoNew.pdf Yes it happens with all pdfs! here's an example. If a sidebar is the bar that opens when pressing F9, no. But it happens also when it is enabled. It happens in al "view" modes: fullscreen, continuous, dual... Could it be a graphic driver error? P.s. I have a mobility radeon 9700. I use the default driver"
what cairo version do you have?
libcairo is 1.4.10, it happened with 1.4.8 and also using the 1.4.2 version from feisty preloaded on gutsy
Created attachment 91641 [details] [review] Patch I don't know whether this bug is related to #314616. Sebastien, could you apply this patch and tell me if it has any effect, please?
the patch doesn't make it work smoothly
oh! :-( what I supposed. It's very difficult to fix this for me, since I can't reproduce it. hmm, do you have an ATI video card? it could be a driver specific problem.
right, the bug is described on http://bugs.freedesktop.org/show_bug.cgi?id=4320
I've noticed the same slowness too on Fedora rawhide with evince-0.9.3-1.fc8. This slowness happens with both ps and pdf files, and I have an nvidia 6600LE video card using xorg 'nv' driver. Opening a ps/pdf file with evince drives X cpu usage up (evince cpu usage goes up too, but not so much as X). This slowness and high cpu usage doesn't happen on Fedora 7 with evince-0.8.2-1.fc7.
hmm, could anyone provide sysprof or oprofile output, please?
I did try to sysprof it some time ago and it looked like the xaa ati bug
(In reply to comment #8) > hmm, could anyone provide sysprof or oprofile output, please? > Is there any quick howto on using these tools?
(In reply to comment #10) > Is there any quick howto on using these tools? > Yes, take a look at http://live.gnome.org/Sysprof Thank you for your help.
Created attachment 93482 [details] sysprof log on opening a pdf file with evince
Created attachment 93483 [details] sysprof log on opening a ps file with evince
comment on the launchpad bug "I fixed this bug adding Option "XAANoOffscreenPixmaps" in the device section of xorg.conf"
(In reply to comment #14) > comment on the launchpad bug > > "I fixed this bug adding > Option "XAANoOffscreenPixmaps" > in the device section of xorg.conf" > Thanks a lot, this fixed it for me too (using xorg 'nv' driver). Can someone here please enlighten me, what are the side-effects of enabling this option, if there is any?
Are you going to revert to rendering to an intermediat GdkPixbuf for 2.20 (if the performance problems aren't fixed)? I've reverted to using Xpdf for now (can't stand the sound skips when the document is redrawn).
(In reply to comment #16) > Are you going to revert to rendering to an intermediat GdkPixbuf for 2.20 (if > the performance problems aren't fixed)? hmm, I'm afraid yes. > I've reverted to using Xpdf for now (can't stand the sound skips when the > document is redrawn). > I see. Doesn't the XAANoOffscreenPixmaps workaround work for you?
(In reply to comment #17) > I see. Doesn't the XAANoOffscreenPixmaps workaround work for you? Haven't tried it yet. Looked around for what other effects it might have a while earlier today though. But if XAANoOffscreenPixmaps is to be considered a temporary solution, it must be set automatically when it can cause slowdowns. And I'm not sure if there are any distros that do that. It's probably wiser to just fix the driver/server problem instead. :)
using XAANoOffscreenPixmaps is not an option, it has a real impact on the video performances and is a non efficient workaround
Ok, good to know.
It seems jrmuizel caught the problem! I've just committed a patch that works for me. Could you guys confirm the problem is also fixed for you with evince from svn trunk, please? Thank you very much for your help.
Confirming (trunk fixes it for me too :) .
confirmed, svn fixes the bug
(In reply to comment #23) > confirmed, svn fixes the bug > (In reply to comment #22) > Confirming (trunk fixes it for me too :) . > Great!, thank you all for your help and your patience.