| Summary: | crash during alt+tab | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Pascal d'Hermilly <pascal> |
| Component: | effects-tabbox | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | czarbug, jorge.adriano, kde, morynicz, thilo, woskimi, wzab01 |
| Priority: | NOR | ||
| Version: | 4.8.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
|
Description
Pascal d'Hermilly
2011-01-30 22:30:40 UTC
bug #261323 related? perhaps. It is using the flip switch. But it has only happened once and I use it all the time. we need a proper way to reproduce in order to investigate the crash. Created attachment 62711 [details]
New crash information added by DrKonqi
kwin (4.7.00 (4.7.0)) on KDE Platform 4.7.00 (4.7.0) using Qt 4.7.2
- What I was doing when the application crashed:
Attached a secons monitor to the PC. On Alt+Tab KWin crashed.
-- Backtrace (Reduced):
#6 0x00007f7c6b26bf8a in KWin::EffectsHandlerImpl::currentTabBoxWindowList (this=<value optimized out>) at ../../kwin/effects.cpp:767
#7 0x00007f7c4edda7e1 in KWin::FlipSwitchEffect::paintScreen (this=0x1991ff0, mask=32, region=..., data=...) at ../../../kwin/effects/flipswitch/flipswitch.cpp:153
#8 0x00007f7c6b26c9f3 in KWin::EffectsHandlerImpl::paintScreen (this=0x2cac500, mask=32, region=<value optimized out>, data=...) at ../../kwin/effects.cpp:212
#9 0x00007f7c69329968 in KWin::Effect::paintScreen (this=<value optimized out>, mask=32, region=<value optimized out>, data=...) at ../../../kwin/libkwineffects/kwineffects.cpp:142
#10 0x00007f7c6b26c9f3 in KWin::EffectsHandlerImpl::paintScreen (this=0x2cac500, mask=32, region=<value optimized out>, data=...) at ../../kwin/effects.cpp:212
*** Bug 281487 has been marked as a duplicate of this bug. *** looks like the currentTabBoxWindowList can contain NULL or invalidated clients?! patch for the NULL case: foreach (Client * c, clients) if (c) ret.append(c->effectWindow()); for the invalidation issue we'd got a problem. To be sure we need better backtraces (best 'd be gdwarf'd ;-) Created attachment 66013 [details]
New crash information added by DrKonqi
kwin (4.7.2 (4.7.2) "release 5") on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.7.4
- What I was doing when the application crashed:
Alt-Tabbing. Windows were of Firefox, also several skype chats and two skype contact lists. Compiz was enabled and alt-tab effect was "Flip Switch". Crash hasn't repeated yet.
-- Backtrace (Reduced):
#6 0x00007f979aa0182a in KWin::EffectsHandlerImpl::currentTabBoxWindowList (this=<optimized out>) at /usr/src/debug/kde-workspace-4.7.2/kwin/effects.cpp:767
#7 0x00007f977e3b6bf6 in KWin::FlipSwitchEffect::paintScreen (this=0x9a1d40, region=..., data=<optimized out>, mask=<optimized out>) at /usr/src/debug/kde-workspace-4.7.2/kwin/effects/flipswitch/flipswitch.cpp:153
#8 0x00007f977e3b8f42 in KWin::FlipSwitchEffect::paintScreen (this=0x9a1d40, mask=544, region=..., data=...) at /usr/src/debug/kde-workspace-4.7.2/kwin/effects/flipswitch/flipswitch.cpp:150
#9 0x00007f979a9fe746 in KWin::EffectsHandlerImpl::paintScreen (this=0x92f190, mask=544, region=<optimized out>, data=...) at /usr/src/debug/kde-workspace-4.7.2/kwin/effects.cpp:212
#10 0x00007f977e36f0a8 in KWin::DesktopGridEffect::paintScreen (this=<optimized out>, mask=544, region=..., data=...) at /usr/src/debug/kde-workspace-4.7.2/kwin/effects/desktopgrid/desktopgrid.cpp:161
*** Bug 293129 has been marked as a duplicate of this bug. *** I can make it happen pretty consistently. Open some windows. open yakuake. alt+tab once and keep holding alt for 1-2 seconds like looking at the window. Release keys and kwin chrashes (2/3 times for me) not here. try to disable the sliding popup effect (assuming your yakuake hides when loosing focus?!) and maybe mention your KDE version... It does not happens when I enable "Keep window open when it looses focus". I'm using KDE 4.8, but apparently I also reported it for 4.6 (original reporter) By now I'm quite sure that the crash happens because a window is "closed". Be it yakuake or a CD-burner dialog(original report) This is from Konsole: pascal@pascal-laptop:~$ kwin --replace OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile OpenGL version string: 2.1 Mesa 7.11 OpenGL shading language version string: 1.20 Driver: Intel GPU class: i965 OpenGL version: 2.1 GLSL version: 1.20 Mesa version: 7.11 X server version: 1.10.4 Linux kernel version: 3.0 Direct rendering: yes Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes Application::crashHandler() called with signal 11; recent crashes: 1 OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile OpenGL version string: 2.1 Mesa 7.11 OpenGL shading language version string: 1.20 Driver: Intel GPU class: i965 OpenGL version: 2.1 GLSL version: 1.20 Mesa version: 7.11 X server version: 1.10.4 Linux kernel version: 3.0 Direct rendering: yes Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes KCrash: Application 'kwin' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/pascal/.kde/socket-pascal-laptop/kdeinit4__0 [1]+ Stopped kwin --replace *** Bug 294378 has been marked as a duplicate of this bug. *** It happens for me too. But i have no pattern yet. I have also configured Meta + Tab to switch desktops. And it happens with this combination too. If i use just mouse then i have no problems. Still happens in 4.8.2 *** Bug 300187 has been marked as a duplicate of this bug. *** has anyone been able to reproduce the crash with 4.9? We fixed a little bit in Alt+Tab and that might be fixed now. I cannot reproduce anymore with kde 4.10 rc2 (In reply to comment #17) > I cannot reproduce anymore with kde 4.10 rc2 this is good news! Thanks for the fast reply. By that I assume we fixed it. If anyone is still able to reproduce, please reopen. |