Summary: | thread library segfault | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Michael Hammond <bugs> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | steve.mckuhr |
Priority: | NOR | ||
Version: | 4.9.4 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Michael Hammond
2013-02-27 20:01:38 UTC
crashes in Client *c = qobject_cast<Client*>(*it); but has already passed Layer l = (*it)->layer(); and const int screen = (*it)->screen(); Smells like stack corruption. You say "some of the time" - do you always get the same backtraces? I have not chased previous crashes. I will get religious about sending bug reports when it happens. seems like it doesn't happen in a reliable way ;-) Setting to waitingforinfo till we have a pattern. Created attachment 78994 [details]
New crash information added by DrKonqi
kwin (4.10.1) on KDE Platform 4.10.1 using Qt 4.8.4
- What I was doing when the application crashed:
Alt-Tab to switch between windows (several windows open, several desktops)
- Unusual behavior I noticed:
Until KWin recovered (short time): task bar and windows margins dissapeared.
-- Backtrace (Reduced):
#7 0x0000003f80462e95 in KWin::Workspace::constrainedStackingOrder (this=this@entry=0x14cd540) at /usr/src/debug/kde-workspace-4.10.1/kwin/layers.cpp:558
#8 0x0000003f80463563 in updateStackingOrder (propagate_new_clients=true, this=0x14cd540) at /usr/src/debug/kde-workspace-4.10.1/kwin/layers.cpp:119
#9 KWin::Workspace::updateStackingOrder (this=0x14cd540, propagate_new_clients=true) at /usr/src/debug/kde-workspace-4.10.1/kwin/layers.cpp:112
#10 0x0000003f804636f0 in blockStackingUpdates (this=<optimized out>, block=<optimized out>) at /usr/src/debug/kde-workspace-4.10.1/kwin/layers.cpp:665
#11 KWin::Workspace::blockStackingUpdates (this=<optimized out>, block=<optimized out>) at /usr/src/debug/kde-workspace-4.10.1/kwin/layers.cpp:657
Is anybody here using composting or - to be more precise - was using compositing at the time the crash occurred? And if so, do you use effects on hiding windows (like eg. "fade")? (In reply to comment #5) > Is anybody here using composting or - to be more precise - was using > compositing at the time the crash occurred? Yes. Compositing type: OpenGL Qt graphics system: Raster Keep window thumbnails: Only for Shown Windows Scale method: Accurate Checked is: - Use OpenGL 2 Shaders > And if so, do you use effects on hiding windows (like eg. "fade")? Yes. I've got Fade 0.2.0. Ok, i thought this was the reason (see bug #317765) - ie. crashes because you're NOT compositing. Dead end then, though :-( *** This bug has been marked as a duplicate of bug 317765 *** |