Bug 337351

Summary:	system settings crash when playing arround in the compositor settings
Product:	[Plasma] kwin	Reporter:	simonlang1984
Component:	compositing	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	crash
Priority:	NOR
Version:	git master
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	systemsettings-20140711-112125.kcrash

Description simonlang1984 2014-07-11 09:28:54 UTC

system settings crashes after playing arround in the compositor settings and clicking very fast on the dialog window appearing when switching from glx to egl
http://goo.gl/CmYCnb


Reproducible: Didn't try

Steps to Reproduce:
1.open system settings
2.  open display configuration
3. compositor
4. rendering background opengl 3.1 
5. switch from opengl interface glx to egl and apply
Actual Results:  
system settings crashed

Expected Results:  
no crash

http://goo.gl/CmYCnb

Comment 1 simonlang1984 2014-07-11 09:29:23 UTC

Created attachment 87686 [details]
systemsettings-20140711-112125.kcrash

Comment 2 Christoph Feck 2014-07-11 11:28:57 UTC

Looks like a Mesa bug.

Thread 1 (Thread 0x7fd4e854f780 (LWP 24499)):
[KCrash Handler]
#6  0x0000000000000000 in ?? ()
#7  0x00007fd4cb324a35 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#8  0x00007fd4cb320a27 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#9  0x00007fd4cb3277ff in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#10 0x00007fd4c16f9792 in QSGBindable::clear (this=0x7fff6b649e50, mode=...) at scenegraph/coreapi/qsgrenderer.cpp:79
#11 0x00007fd4c16e4933 in QSGBatchRenderer::Renderer::renderBatches (this=0x2945370) at scenegraph/coreapi/qsgbatchrenderer.cpp:2246
#12 0x00007fd4c16e5e40 in QSGBatchRenderer::Renderer::render (this=0x2945370) at scenegraph/coreapi/qsgbatchrenderer.cpp:2433
#13 0x00007fd4c16f9ffe in QSGRenderer::renderScene (this=0x2945370, bindable=...) at scenegraph/coreapi/qsgrenderer.cpp:261
#14 0x00007fd4c171349f in QSGRenderContext::renderNextFrame (this=0x2201cc0, renderer=0x2945370, fboId=8) at scenegraph/qsgcontext.cpp:354
#15 0x00007fd4c176a744 in QQuickWindowPrivate::renderSceneGraph (this=0x22e0160, size=...) at items/qquickwindow.cpp:386
#16 0x00007fd4c177b10f in QQuickRenderControl::render (this=0x2149d50) at items/qquickrendercontrol.cpp:194
#17 0x00007fd4b08dd332 in QQuickWidget::resizeEvent (this=0x1fa9ee0, e=0x7fff6b64a610) at qquickwidget.cpp:890
#18 0x00007fd4e5df1921 in QWidget::event (this=0x1fa9ee0, event=0x7fff6b64a610) at kernel/qwidget.cpp:8126

Comment 3 Martin Flöser 2014-07-11 11:38:53 UTC

something is fishy here - the compositor KCM doesn't use QtQuick any more. But the backtrace indicates QtQuick usage.

Comment 4 Thomas Lübking 2014-07-11 13:34:49 UTC

But the effects kcm (and probably some others?) do - it's not clear which one, just *some* QtQuick scene updates (and probably runs into a context collision bug in the driver)

@Simon, do you already have "kcmshell5"?

Comment 5 simonlang1984 2014-07-11 13:40:12 UTC

@thomas

no i have not yet kcmshell5

Comment 6 Martin Flöser 2015-01-07 11:07:31 UTC

marking as driver bug.