Bug 113394

Summary:	kded eats CPU to a crawl. Is it proxy to blame?
Product:	[Unmaintained] kdelibs	Reporter:	apodtele
Component:	kded	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description apodtele 2005-09-26 23:15:50 UTC

Version:            (using KDE KDE 3.4.2)
Installed from:    Fedora RPMs
Compiler:          gcc 4.0.1 
OS:                Linux

Prolog:

I used to browse FTP sites with konqueror, make multiple selections there, drug-n-drop them into console's "wget -N" (because I care about timestamps). I enjoyed it - selecting with mouse or shift-arrows worked fast-n-smooth.

Main story:

Recently I enabled proxy via proxy configuration URL. Selecting just a few items on any FTP site takes pretty much forever. It's basically unusable. So I fired up top to see who eats CPU - it was kded. It is actually spectacular to see how it struggles while I drag the mouse over the filenames trying to select. Interestingly, proxy was probably not even used, because I was never authenticated.

Epilog:

I turned off proxy option. Just like that (no need to restart) I enjoy my life again, but I kinda need my proxy.

Comment 1 Praedor Tempus 2006-03-25 16:45:16 UTC

I'm running KDE 3.4.2 in Mandriva 2006, AMD64 version (x86_64).  As soon as KDE starts, kded runs up the cpu to 70-90% in cycles.  Apps start very slowly.  I have plenty of memory and virtually no swap is used.  Doing a "dcop kded" I get:

KDebug
KDirNotify-1
KDirNotify-2
KDirNotify-3
KDirNotify-4
MainApplication-Interface
dnssdwatcher
katd
kbuildsycoca
kded
ksycoca
kwalletd
kwrited
mdvdirnotify
mediamanager
networkstatus
qt/kded
remotedirnotify
systemdirnotify

I have the equivalent system (same kde version and services running) on my Pentium M laptop but kded is well-behaved on it.

Comment 2 Thiago Macieira 2006-04-01 23:01:53 UTC

"katd" is the culprit. Disable it, uninstall it or upgrade to a version that doesn't consume that much CPU.

Mandriva should never have shipped it in pre-alpha stage.

Comment 3 apodtele 2007-11-16 19:13:47 UTC

This is CRAP. Comment #1 just highjacked my original bug with something which has NOTHING to do with my problem, then comment #2 happily "resolved" the irrelevant issue.

kded still hogs CPU with PROXY connections... I don't know how, I doubt that it should.