Version: 4.0 (using KDE 3.1.0) Installed from: SuSE Compiler: gcc version 2.95.3 20010315 (SuSE) OS: Linux (i686) release 2.4.18 When I visit the page http://datacruz.com/~kyledtc/, the cpu load of X and the corresponding kdeinit process rises sky-highand bogs down the whole system. The culprit is probably the JavaScript on that page. 11:17pm up 9:29, 1 user, load average: 1.97, 1.55, 1.33 80 processes: 74 sleeping, 6 running, 0 zombie, 0 stopped CPU states: 87.0% user, 1.3% system, 11.5% nice, 0.0% idle Mem: 514244K av, 492328K used, 21916K free Swap: 257032K av, 12704K used, 244328K free PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CMD 894 root 20 0 112M 38M 1904 R 68.3 7.6 11:28 X 25970 mss 12 0 23012 22M 16172 R 13.5 4.4 0:38 kdeinit 225 dnetc 20 19 488 476 412 R N 11.5 0.0 529:10 dnetc
wfm (but wouldn't wonder, if that script eats slower CPUs)
Here [2] is another page which bogs down my system; not as extreme as the other previous but the DHTML newsticker on the left is still not nice to my system (now KDE 3.1.2 on an Athlon 1200). [2]http://www.shz.de/?RUBRIKID=745&MID=30&REDID=155909
The guilty party seems to be the script: setTimeout("Fireworks()",20); . I don't know how to classify this, though. There is a script which is trying to use a lot of cpu, how should we handle it? luis.
And two other sites: A animated picture is moved by JavaScript http://www.battle.net/diablo2exp/ A JavaScript NewsTicker on http://www.chip.de/
Subject: High CPU load on http://datacruz.com/~kyledtc/ http://datacruz.com/~kyledtc/: Same problem with actual CVS (KDE 3.1.94). But mozilla isn't better :-). Regards, Andreas Hartmann
CPU load is 30% in my Athlon 1300 with KDE 3.2.1. I don't think this is a bug in konqueror.
You're right, on KDE 3.2.1 it doesn't take down the whole system anymore; seems like there was some improvement on that front. But it still renders Konqi useless. Mozilla 1.6 behaves a bit better: You can still use the menus and close the tab without hassle. So the bug (or wish?) here is that Konqi should prevent malicious (or stupidly coded) websites from DOSing your box.
I've been observing the same thing. If I have several Konquerors with several tabs open, my system (P4 2.0 GHz with 512 MB of RAM, total memory 55% free/swap space 89% as reported by the new KInfoCenter) climbs all the way up to a load average getting sometimes into the 7s and 8s. This is really horrible! When I first resolved to make some real observations about and report this, I figured it was probably javascript stuff and animated GIFs or flashes wasting resources, but I just saw the same thing happen in the following scenario. One Konqueror. Two tabs. One of them a google groups search displaying an article (URL is long and ugly, but it's just a page full of text), the other a look at http://www.debianplanet.org/ Neither one of these is animating anything, neither one is using javascript (I just looked at the sources) and yet: top - 12:05:05 up 1 day, 19:03, 3 users, load average: 1.76, 1.93, 1.19 Tasks: 104 total, 4 running, 100 sleeping, 0 stopped, 0 zombie Cpu(s): 2.6% user, 3.3% system, 0.0% nice, 94.0% idle I killed that Konqueror (leaving this one I'm typing into running) and instantly saw: top - 12:15:10 up 1 day, 19:13, 3 users, load average: 0.16, 0.35, 0.65 Tasks: 109 total, 1 running, 108 sleeping, 0 stopped, 0 zombie Cpu(s): 2.0% user, 1.3% system, 0.0% nice, 96.7% idle Pow. Dropped right off, like flipping off a switch. I think there's something to this problem. Unfortunately, starting them back up and looking at the same pages a second time didn't flip the switch in the other direction. The load average didn't blip. It seems to take Konqueror sitting there in the background for awhile to drive up the CPU load. I really only notice it when I'm typing a message in KMail or Konqueror, and suddenly the system bogs down so much that it's like typing on a PII-233. Look at the spikey load average, go kill Konqueror and resume the message with this machine's normal responsiveness. That's my most typical scenario, and it's happening quite a lot lately. Especially since the upgrade to 3.2.2. (Which I'm running on a clean install, incidentally. This install has never had anything other than 3.2.2.) Anyway, I know these are just vague observations, and not especially useful. I'd be happy to try to track this down more properly if I had a better idea what to look for.
Duplicate *** This bug has been marked as a duplicate of 53114 ***