Bug 257901

Summary: kwin 100% CPU on resume from suspend
Product: [Plasma] kwin Reporter: Tom <tcl-kde>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash Keywords: investigated, triaged
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Tom 2010-11-25 18:48:05 UTC 
Application: kwin (4.5.1 (KDE 4.5.1))
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.36-020636-generic i686
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed:
After resume from suspend kwin was using 100% of one cpu.  X took about 35% of the other.  This has occurred a few times (but not always) when I have resumed from suspend recently. 
- Unusual behavior I noticed:
Desktop was very slow.  Crash occurred when I executed kwin --replace 

NVIDIA driver 260.19.21
Xorg 1.9.0

BTW if this is useful this is running
2281     1  0 Nov24 ?        00:00:06 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session

The crash can be reproduced some of the time.

-- Backtrace:
Application: KWin (kwin), signal: Aborted
[KCrash Handler]
#7  0xb78d9424 in __kernel_vsyscall ()
#8  0xb768b941 in raise () from /lib/libc.so.6
#9  0xb768ee42 in abort () from /lib/libc.so.6
#10 0xb67cb2dc in qt_message_output (msgType=QtFatalMsg, buf=0x8ab83f0 "kwin(20361): Session bus not found \n") at global/qglobal.cpp:2259
#11 0xb737d0e5 in QDebug::~QDebug (this=0xbf880c30, __in_chrg=<value optimized out>) at /usr/include/qt4/QtCore/qdebug.h:85
#12 0xb7483c7f in KApplicationPrivate::init (this=0x8acd5d0, GUIenabled=true) at ../../kdeui/kernel/kapplication.cpp:513
#13 0xb7485527 in KApplication::KApplication (this=0xbf8812a4, GUIenabled=true) at ../../kdeui/kernel/kapplication.cpp:351
#14 0xb7820218 in KWin::Application::Application (this=0xbf8812a4) at ../../kwin/main.cpp:246
#15 0xb78218cc in kdemain (argc=4, argv=0xbf881504) at ../../kwin/main.cpp:510
#16 0x080485ab in main (argc=4, argv=0xbf881504) at kwin_dummy.cpp:3

Possible duplicates by query: bug 252910, bug 246404.

Reported using DrKonqi
Comment 1 Thomas Lübking 2010-11-25 23:27:23 UTC 
is it possible to run "qdbus" in this situation? does it reply the normal output (list of services)

i assume you're using compositing? do you get away by a suspend/resume (shift+alt+f12, twice)?
Comment 2 Tom 2010-11-27 09:18:04 UTC 
It does appear to be compositing.  After two shift+alt+F12 sequences all returns to normal including qdbus output (and kwin doesn't crash).
Comment 3 Thomas Lübking 2010-11-27 16:36:41 UTC 
simple workaround: suspend compositing _before_ suspending the system and resume it _after_ system resume (you can use the pm scripts for this)

to investigate, you'll have to install eg. sysprof and monitor the system load.
for a quick investigation you can also just attach gdb and call a backtrace (kwin is likely in the expensive loop :-)
Comment 4 Martin Flöser 2010-12-18 12:18:59 UTC 
we need more info to investigate this issue.
Comment 5 Andrew Crouthamel 2018-09-20 21:53:05 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-21 05:25:14 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!