Bug 78212 - kwin falls into a loop keeping average CPU load higher than 2.0 after closing a window
Summary: kwin falls into a loop keeping average CPU load higher than 2.0 after closing...
Status: RESOLVED DUPLICATE of bug 64671
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-22 15:18 UTC by Piotr Kolaczkowski
Modified: 2004-03-22 15:24 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Piotr Kolaczkowski 2004-03-22 15:18:24 UTC
Version:            (using KDE KDE 3.2.1)
Installed from:    Compiled From Sources
Compiler:          gcc 3.1.3 
OS:          Linux

Sometimes, with probability 30% - 60%, after closing a Konsole window (or some other app's) kwin falls into a loop and together with kded and X raises CPU load to more than 2. This loop cannot be broken other way than restarting X server and KDE. Just closing a session in Konsole also results in the same behaviour. This is not the X bug, because it doesn't occur in other window managers. Note that opening windows, and "normal work" with apps is also ok.

The problem exists both in KDE 3.2.0 and 3.2.1, regardless if it was compiled from source or installed from a  binary package (Slackware). 

To reproduce:
1. open Konsole, run top
2. open another Konsole
3. close "another Konsole"
4. wait a few seconds
5. if you don't see something like that
  
   1040 root      16 -10 68868  18m 3244 R  30.5  1.9   6:54.36 X
 7334 pkolaczk  15   0 13672  13m  11m R  22.2  1.3   2:34.12 kdeinit
24950 pkolaczk   9   0 13948  13m  11m R  47.0  1.4   0:00.33 kdeinit
...

then jump to point 2.
Comment 1 Piotr Kolaczkowski 2004-03-22 15:19:55 UTC
Oh, I forgot: Simply killing the kwin helps...
Comment 2 Lubos Lunak 2004-03-22 15:24:34 UTC

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