Bug 310117

Summary: kwin crash
Product: [Plasma] kwin Reporter: Kai Bolay <kai>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash CC: kai
Priority: NOR Keywords: triaged
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description Kai Bolay 2012-11-14 20:52:59 UTC 
Application: kwin (4.8.5 (4.8.5))
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-32-generic x86_64
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:

establishing a VPN connection, clicking reload in the Chrome browser

The crash can be reproduced some of the time.

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
[KCrash Handler]
#6  width (this=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qrect.h:304
#7  QRegionPrivate (r=..., this=0x2b26d00) at painting/qregion.cpp:1105
#8  QRegion::QRegion (this=0x7fffea27c5c0, r=..., t=QRegion::Rectangle) at painting/qregion.cpp:3850
#9  0x00007f643ce6e617 in QRegion::operator+= (this=0x7fffea27c7b0, r=...) at painting/qregion.cpp:4091
#10 0x00007f641fda2fbe in KWin::BlurEffect::expand (this=0x2377bd0, region=...) at ../../../kwin/effects/blur/blur.cpp:183
#11 0x00007f641fda54f5 in KWin::BlurEffect::prePaintWindow (this=0x2377bd0, w=0x26fa840, data=..., time=<optimized out>) at ../../../kwin/effects/blur/blur.cpp:279
#12 0x00007f64425252a2 in KWin::EffectsHandlerImpl::prePaintWindow (this=0x244c1c0, w=<optimized out>, data=..., time=<optimized out>) at ../../kwin/effects.cpp:237
#13 0x00007f641fd8f190 in KWin::TranslucencyEffect::prePaintWindow (this=0x2580050, w=0x26fa840, data=..., time=1) at ../../../kwin/effects/translucency/translucency.cpp:102
#14 0x00007f64425252a2 in KWin::EffectsHandlerImpl::prePaintWindow (this=0x244c1c0, w=<optimized out>, data=..., time=<optimized out>) at ../../kwin/effects.cpp:237
#15 0x00007f6442502fb6 in KWin::Scene::paintSimpleScreen (this=0x20a9130, orig_mask=8, region=...) at ../../kwin/scene.cpp:285
#16 0x00007f6442501a14 in KWin::Scene::finalPaintScreen (this=0x20a9130, mask=8, region=..., data=...) at ../../kwin/scene.cpp:198
#17 0x00007f64425253f7 in KWin::EffectsHandlerImpl::paintScreen (this=0x244c1c0, mask=8, region=..., data=...) at ../../kwin/effects.cpp:222
#18 0x00007f64402eb508 in KWin::Effect::paintScreen (this=<optimized out>, mask=8, region=..., data=...) at ../../../kwin/libkwineffects/kwineffects.cpp:142
#19 0x00007f644252539b in KWin::EffectsHandlerImpl::paintScreen (this=0x244c1c0, mask=8, region=..., data=...) at ../../kwin/effects.cpp:219
#20 0x00007f64402eb508 in KWin::Effect::paintScreen (this=<optimized out>, mask=8, region=..., data=...) at ../../../kwin/libkwineffects/kwineffects.cpp:142
#21 0x00007f644252539b in KWin::EffectsHandlerImpl::paintScreen (this=0x244c1c0, mask=8, region=..., data=...) at ../../kwin/effects.cpp:219
#22 0x00007f6442504a25 in KWin::Scene::paintScreen (this=0x20a9130, mask=0x7fffea27d0f8, region=0x7fffea27d1e0) at ../../kwin/scene.cpp:156
#23 0x00007f644251a8ed in KWin::SceneOpenGL::paint (this=0x20a9130, damage=..., toplevels=...) at ../../kwin/scene_opengl_glx.cpp:459
#24 0x00007f64424fe628 in KWin::Workspace::performCompositing (this=0x2063ef0) at ../../kwin/composite.cpp:417
#25 0x00007f643d966179 in QObject::event (this=0x2063ef0, e=<optimized out>) at kernel/qobject.cpp:1157
#26 0x00007f643cccf894 in notify_helper (e=0x7fffea27d8c0, receiver=0x2063ef0, this=0x1ef57b0) at kernel/qapplication.cpp:4559
#27 QApplicationPrivate::notify_helper (this=0x1ef57b0, receiver=0x2063ef0, e=0x7fffea27d8c0) at kernel/qapplication.cpp:4531
#28 0x00007f643ccd4713 in QApplication::notify (this=0x7fffea27dce0, receiver=0x2063ef0, e=0x7fffea27d8c0) at kernel/qapplication.cpp:4420
#29 0x00007f6441c613f6 in KApplication::notify (this=0x7fffea27dce0, receiver=0x2063ef0, event=0x7fffea27d8c0) at ../../kdeui/kernel/kapplication.cpp:311
#30 0x00007f643d94ce9c in QCoreApplication::notifyInternal (this=0x7fffea27dce0, receiver=0x2063ef0, event=0x7fffea27d8c0) at kernel/qcoreapplication.cpp:876
#31 0x00007f643d97e1f2 in sendEvent (event=0x7fffea27d8c0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#32 QTimerInfoList::activateTimers (this=0x1ef63d8) at kernel/qeventdispatcher_unix.cpp:611
#33 0x00007f643d97ecb4 in QEventDispatcherUNIX::processEvents (this=0x1ea9ad0, flags=...) at kernel/qeventdispatcher_unix.cpp:930
#34 0x00007f643cd78bf8 in QEventDispatcherX11::processEvents (this=0x1ea9ad0, flags=...) at kernel/qeventdispatcher_x11.cpp:152
#35 0x00007f643d94bc82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#36 0x00007f643d94bed7 in QEventLoop::exec (this=0x7fffea27dc20, flags=...) at kernel/qeventloop.cpp:204
#37 0x00007f643d950f67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#38 0x00007f64424b3c36 in kdemain (argc=<optimized out>, argv=<optimized out>) at ../../kwin/main.cpp:541
#39 0x00007f64420b576d in __libc_start_main (main=0x400630 <main(int, char**)>, argc=3, ubp_av=0x7fffea27e408, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffea27e3f8) at libc-start.c:226
#40 0x0000000000400661 in _start ()

Reported using DrKonqi
Comment 1 Thomas Lübking 2012-11-14 21:49:40 UTC 
stack/heap corruption or bug in Qt.

please elaborate on the VPN condition, do you run a remote KDE or did you just establish a VPN (proxy)

Also you sa it can be reproduced "some of the time". in this case please provide more backtraces or confirm they look all the same.
Comment 2 Kai Bolay 2012-11-14 22:20:32 UTC 
(In reply to comment #1)

 > please elaborate on the VPN condition, do you run a remote KDE or did you
 > just establish a VPN (proxy)

I'm just running KDE locally. The crash happened while in the background a script was running that established a VPN connection - I mentioned this because a changing network configuration might be related to the problem.

 > Also you sa it can be reproduced "some of the time". in this case please
 > provide more backtraces or confirm they look all the same.

kwin crashes for me about once per week. I'll make sure to capture stack traces every time going forward and I'll update this bug.
Comment 3 Thomas Lübking 2012-11-14 22:57:00 UTC 
(In reply to comment #2)
> kwin crashes for me about once per week.

you're aware that that is not supposed to be normal? ;-)

do you alter the screen resolution or refresh rate from time to time?
Comment 4 Kai Bolay 2012-11-15 00:08:40 UTC 
(In reply to comment #3)
> (In reply to comment #2)
> > kwin crashes for me about once per week.
> 
> you're aware that that is not supposed to be normal? ;-)

Yes, but it restarts and I can continue working normally - so I did not bother filing a bug report earlier.

> do you alter the screen resolution or refresh rate from time to time?

No.
Comment 5 Thomas Lübking 2012-11-15 00:39:03 UTC 
Please don't do that - bugs don't get fixed by not reporting them.
Comment 6 Martin Flöser 2012-12-29 08:48:37 UTC 
do the other crash reports look the same as this one?

Could you please attach the output of:
qdbus org.kde.kwin /KWin supportInformation
Comment 7 Martin Flöser 2013-01-17 15:33:23 UTC 
please answer questions from comment #6. Otherwise we are not able to investigate the issue.
Comment 8 Kai Bolay 2013-01-17 18:44:59 UTC 
(In reply to comment #6)

 > do the other crash reports look the same as this one?

Back when I reported this I got similar crashes frequently. Now when my machine crashes (which unfortunately seems to happen about once a week) it drops to the text console and spews out a lot of stuff which looks like kernel-level debugging information - with no apparent way to capture and report that information :-(

So I've been waiting for a KWin crash to collect a bug report to compare, but so far, no luck.

> Could you please attach the output of:
> qdbus org.kde.kwin /KWin supportInformation

That doesn't look helpful either:

$ qdbus org.kde.kwin /KWin supportInformation
Error: org.freedesktop.DBus.Error.UnknownMethod
No such method 'supportInformation' in any interface at object path '/KWin' (signature '')

Sorry! I'll update this bug if and when I'm able to capture some more useful information.
Comment 9 Martin Flöser 2013-01-17 18:59:08 UTC 
(In reply to comment #8)
> (In reply to comment #6)
> 
>  > do the other crash reports look the same as this one?
> 
> Back when I reported this I got similar crashes frequently. Now when my
> machine crashes (which unfortunately seems to happen about once a week) it
> drops to the text console and spews out a lot of stuff which looks like
> kernel-level debugging information - with no apparent way to capture and
> report that information :-(
oh that doesn't sound good. I would suggest to get support on this issue and I would not be surprised if the problem is related.

First thing I recommend to check: memory. The crash here looks like a memory corruption and kernel panics could also be caused by this. Also watch out whether the system is over heating. That are the rule of thumb suggestions I can do, for anything more: get proper support.
> 
> So I've been waiting for a KWin crash to collect a bug report to compare,
> but so far, no luck.
> 
> > Could you please attach the output of:
> > qdbus org.kde.kwin /KWin supportInformation
> 
> That doesn't look helpful either:
> 
> $ qdbus org.kde.kwin /KWin supportInformation
> Error: org.freedesktop.DBus.Error.UnknownMethod
> No such method 'supportInformation' in any interface at object path '/KWin'
> (signature '')
> 
> Sorry! I'll update this bug if and when I'm able to capture some more useful
> information.
ah you are still on 4.8. This was introduced in 4.9
Comment 10 Kai Bolay 2013-02-17 19:26:29 UTC 
Created attachment 77388 [details]
New crash information added by DrKonqi

kwin (4.8.5 (4.8.5)) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.1

crashes are more rare now. This one happened just after waking the laptop up and launching "vncviewer"

-- Backtrace (Reduced):
#6  0x00007ffa0557f943 in intel_prepare_render () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#7  0x00007ffa055993f6 in brw_draw_prims () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
[...]
#9  0x00007ffa1d9a9ed7 in KWin::GLVertexBufferPrivate::corePainting (this=0x155d2f0, region=..., primitiveMode=4) at ../../../kwin/libkwineffects/kwinglutils.cpp:1189
#10 0x00007ffa1d9a9fd5 in KWin::GLVertexBuffer::render (this=0x1515920, region=..., primitiveMode=4) at ../../../kwin/libkwineffects/kwinglutils.cpp:1298
#11 0x00007ffa2185a9ef in renderQuads (normalized=<optimized out>, tex=<optimized out>, quads=..., region=..., this=<optimized out>) at ../../kwin/scene_opengl.cpp:788
Comment 11 Thomas Lübking 2013-02-17 20:05:08 UTC 
Latest stacktrace (if always looking like this) is an intel bug, see also eg. https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/966744
and we've similar crashes somewhere.

Do all stacktraces look like this?
Comment 12 Andrew Crouthamel 2018-09-24 02:05:38 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 13 Andrew Crouthamel 2018-10-27 03:54:42 UTC 
Dear Bug Submitter,

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!