Bug 285634

Summary: kwin occasionally crashes in KWin::Deleted::create on logout
Product: [Plasma] kwin Reporter: Daniel Eklöf <daniel>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: 4.7.3   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: kwin crash backtrace

Description Daniel Eklöf 2011-11-03 10:54:53 UTC
Created attachment 65190 [details]
kwin crash backtrace

Version:           4.7.3 (using KDE 4.7.3) 
OS:                Linux

After upgrading to KDE 4.7.3, I started seeing occasional crashes in kwin when logging out. It happens ~75% of the times.

This is the first KDE release compiled against QT-4.8 (RC1). I'm mentioning that since there has been a couple of other qlist related bugs that didn't show up until kde was recompiled against the new qt version.

#6  KWin::Deleted::create (c=0xff000000) at /mnt/ram/kde-workspace-4.7.3/kwin/deleted.cpp:52
#7  0x00007f2e9a144130 in KWin::Unmanaged::release (this=0xff000000) at /mnt/ram/kde-workspace-4.7.3/kwin/unmanaged.cpp:84
#8  0x00007f2e9a0c4442 in KWin::Workspace::~Workspace (this=0x1228b30, __in_chrg=<value optimized out>) at /mnt/ram/kde-workspace-4.7.3/kwin/workspace.cpp:542
#9  0x00007f2e9a0c4969 in KWin::Workspace::~Workspace (this=0x1228b30, __in_chrg=<value optimized out>) at /mnt/ram/kde-workspace-4.7.3/kwin/workspace.cpp:574
#10 0x00007f2e9a0e21d3 in KWin::Application::~Application (this=0x7fffbc100960, __in_chrg=<value optimized out>) at /mnt/ram/kde-workspace-4.7.3/kwin/main.cpp:338


Reproducible: Sometimes

Steps to Reproduce:
Log in. Log out. In my session I have the following programs running:

akregator, kmail, kopete, kmix, networkmanager plasma applet, korganizer reminder daemon.

Actual Results:  
kwin segfaults

Expected Results:  
kwin shouldn't segfault.

KDE-4.7.3
QT-4.8rc1
Linux 3.1

KDE compiled with gcc-4.6.2.
Comment 1 Thomas Lübking 2011-11-03 14:26:22 UTC
*** This bug has been marked as a duplicate of bug 282933 ***