Bug 61533 - Selecting text in Konqueror puts excessive load on X
Summary: Selecting text in Konqueror puts excessive load on X
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: khtml renderer (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR minor
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-22 12:42 UTC by cb-kde
Modified: 2006-08-27 10:57 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cb-kde 2003-07-22 12:42:04 UTC
Version:           Recent CVS from KDE_3_1_BRANCH (using KDE KDE 3.1.3)
Installed from:    Compiled From Sources
Compiler:          gcc version 3.3.1 20030626 (Debian prerelease)  
OS:          Linux

When selecting text in the Konqueror web browser, XFree86 can use a large amount of CPU time.

To reproduce.
Open konqueror, and go to a web page (eg http://slashdot.org)
open xterm, so that you can see the xterm and some part of the konqueror window which contains text, and run top.
Hold down the left mouse button and wiggle the mouse around so that text is selected. Keep the mouse moving and do not release the left mouse button.
Top will show that X is using at least 80% of CPU time.

I can reproduce this on my laptop 333MHz, XFree 4.2 with neomagic graphics and on my desktop 1.2GHz, XFree 4.3 and Radeon 9100 graphics. I'm using fontconfig anti-aliased text on both.

Expected behaviour is that this causes very little load on the system. Perhaps all that is needed is to require a short delay between selection area redraws?
Comment 1 Thiago Macieira 2003-07-22 12:53:20 UTC
My system generates a 30% load by X, using approximately 50% of the CPU 
altogether (I have lots of other programs running). 
 
I'm using Konqueror from CVS HEAD, along with XFree86 4.3.0, anti-aliased 
fonts. It's an Athlon 1.4 GHz. 
Comment 2 Amand Tihon 2003-08-04 15:35:04 UTC
Using Konqueror from KDE 3.1.3, Xfree 4.3.0, playing with selection makes 
XFree to take 70-80% of the CPU, kdeinit taking between 15 and 20%. 
 
The figures are similars on an Athlon 850 and a P4 1GHz. Fonts are 
anti-aliased. 
Comment 3 Stephan Kulow 2003-10-22 13:35:25 UTC
I can confirm the raised load, but I don't consider it really important. 
After all it doesn't take away functionality
Comment 4 Stephan Kulow 2003-10-27 14:52:49 UTC

*** This bug has been marked as a duplicate of 55941 ***
Comment 5 cb-kde 2004-04-14 08:45:26 UTC
#55941 is reported as fixed in 3.2.1, but I can still reproduce this.
Comment 6 Marijn Schouten 2006-04-17 19:39:06 UTC
I can confirm on 3.5.2 on amd64 3200+ that holding down mouse button and moving it around on slashdot as described above, I was able to get X to a maximum of 80% CPU usage and konqueror to a maximum of 22%, obviously not simultaneously. No loss in responsiveness or lag or anything bad apart from the high load statistic is experienced.
Comment 7 Lubos Lunak 2006-08-26 18:55:11 UTC
RESOLVED NOTAREALPROBLEM
Comment 8 Clarence Dang 2006-08-27 01:06:21 UTC
On Sunday 27 August 2006 02:55, Lubos Lunak wrote:
> RESOLVED NOTAREALPROBLEM


It really is a problem and it's not minor.  You won't believe how irritating 
it is not being able to select text.  But I did see a commit regarding that 
at some point in the 3.5 branch so will test that and see.
Comment 9 Lubos Lunak 2006-08-27 10:57:01 UTC
"When selecting text in the Konqueror web browser, XFree86 can use a large amount of CPU time." - the bugreport is not about being able to select text, the bugreport is about it needing some CPU activity, which is to be expected.