Bug 65286

Summary:	kded and kwin eventually use 100% CPU when laptop battery monitor running
Product:	[Plasma] kwin	Reporter:	Carl Thompson <cet>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Carl Thompson 2003-10-01 03:30:07 UTC

Version:            (using KDE KDE 3.1.92)
Installed from:    Compiled From Sources

When the KDE laptop battery monitor is running, kded and kwin eventually (after 2 - 10 minutes on my system) take up 100% cpu between.  This is not a gradual increase, but a sudden jump to using all available CPU.  It only happens when the battery monitor is running, and it always seems to happen (eventually) if the battery monitor is set to start automatically on KDE startup.  If kded is started manually after KDE startup and then the battery monitor is turned on, it sometimes happens (eventually) but apparently not always.  When this occurs both kded and kwin will start to use as much CPU as they can.

Comment 1 Carl Thompson 2003-10-01 03:30:45 UTC

This is new in KDE 3.2 alpha 1 and 3.2 alpha 2.

Comment 2 Carl Thompson 2003-10-01 03:43:39 UTC

strace output of kded and kwin when this is happening can be found at http://carlthompson.net/
kded.strace and http://carlthompson.net/kded.strace respectively.

Comment 3 Waldo Bastian 2003-10-01 09:46:26 UTC

Looping on some sort of X interaction.

Comment 4 Lubos Lunak 2003-10-01 12:55:12 UTC

Duplicate. And the straces are unfortunately useless, until I start learning reading X protocol 
from raw data :-/. If you could provide a backtrace that shows something interesting, it would 
be more useful. 
 

*** This bug has been marked as a duplicate of 64671 ***