Bug 134776

Summary:	opening digg.com registration page in Konqueror causes high X CPU usage
Product:	[Applications] konqueror	Reporter:	Yaohan Chen <yaohan.chen>
Component:	general	Assignee:	Konqueror Developers <konq-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	did.hoarau, finex, kfunk
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Yaohan Chen 2006-09-28 09:00:29 UTC

Version:            (using KDE KDE 3.5.4)
Installed from:    Slackware Packages
OS:                Linux

When I open digg.com's register page <http://www.digg.com/register> in Konqueror, the X process's CPU usage becomes very high, and the desktop becomes very unresponsive. X CPU usage drops to normal after I kill the Konqueror process.

Comment 1 Philip Rodrigues 2006-09-28 10:52:02 UTC

Can't reproduce on r588250.

Comment 2 Tim Groeneveld 2006-09-28 11:20:03 UTC

I am able to reproduce this on KDE 3.5.4 on AegeanLinux, using latest packages. Strange :/

(KDE 3.5.4, Xorg 7.0, SiS, Kernel 2.6.17.13)

Comment 3 Tommi Tervo 2006-09-28 11:26:57 UTC

Cannot reproduce either, svn r588k. Possible dupe of this bug:
http://bugs.kde.org/show_bug.cgi?id=133529

Comment 4 Thomas McGuire 2007-01-28 17:23:03 UTC

*** Bug 135699 has been marked as a duplicate of this bug. ***

Comment 5 Kevin Funk 2007-02-22 18:25:15 UTC

Still reproducable in 3.5.6.
digg.com is very laggy, renders slowly.
Another example for this is AVM's webinterface of their Fritz!Box (a WLAN router); there's a lot of javascript with inline frames and so on.
Shall I file a separate bug for this?

Comment 6 Sami Cokar 2008-05-05 05:08:34 UTC

KDE 3.5.9
KDE 4.0.3
Kubuntu 8.04

able to complete registration with no noticeable impact on KDE environment

Comment 7 FiNeX 2008-06-01 19:05:17 UTC

I confirm what Sami said.
Both KDE 3.5.9 and KDE 4 (trunk) render correctly digg.com.

Comment 8 FiNeX 2008-06-01 19:06:22 UTC

@Kevin: yes, please if you still have issues with that web-interface report a new bug against it.

Thanks a lot!