GNOME Bugzilla – Bug 756366
High cpu usage *after* selecting text
Last modified: 2015-10-12 16:03:50 UTC
To reproduce: 1.) Get any PDF file, for example this one: https://www.opengl.org/registry/doc/glspec45.core.pdf 2.) Open it with evince. 3.) Select some text with your mouse. 4.) Open gnome-system-monitor and notice how evince is now eating cpu cycles. The amount of cpu usage depends on the length of your selection. Selecting a whole paragraph results in more cpu usage than selecting a single word. I use Arch linux with Cinnamon and evince 3.18.0. Notice that the high cpu load occurs when the selection has already been made and the mouse button has been released again (not only during selecting). So this is *not* the same as bug #732404. You can even minimize evince and still have high cpu load. The cpu usage goes back to 0% again when you remove the selection.
This does not happen on my Manjaro system with Evince 3.16.1.
Thanks for taking the time to report this. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 732404 ***
Opps. I just noticed it is *after* the mouse is released. Re-opening.
I can reproduce the bug on Archlinux with evince 3.18, the cpu stays to about 7% when text is selected, and 0% when text is not selected.
Bug confirmed as well on OpenBSD.
I think this bug is fixed by commit https://git.gnome.org/browse/evince/commit/?id=1987f04ea36329b1bd61d053a19d9e341e0454ce can you confirm it's the same bug?
(In reply to José Aliste from comment #6) > I think this bug is fixed by commit > https://git.gnome.org/browse/evince/commit/ > ?id=1987f04ea36329b1bd61d053a19d9e341e0454ce > > > can you confirm it's the same bug? Oh yes, I can :-) That commit does indeed fix the issue here. Thank you José.
*** This bug has been marked as a duplicate of bug 755442 ***