Bug 218560

Summary:	SIGBUS in KPixmapCache::Private::mmapFile() when KPixmapCache::deleteCache() is called.
Product:	[Unmaintained] kdelibs	Reporter:	Gilboa Davara <gilboad>
Component:	kdeui	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	fredrik, kwin-bugs-null
Priority:	NOR
Version:	SVN
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Composite start/stop script xsession errors.

Description Gilboa Davara 2009-12-13 20:29:02 UTC

Version:           kdebase-workspace-4.3.3-7.fc11.x86_64 (using KDE 4.3.3)
Compiler:          gcc-4.4.1 
OS:                Linux
Installed from:    Fedora RPMs

I've got a short scripts that toggles composite when playing games / showing videos / working with multiple windows. (Attached).
I've noticed that fairly consistently, if I start/stop composite for more than say, 20 times in a single session, screen saver no longer works. Screen saver dialog box works, TEST works, but the screensaver never starts by itself, and neither the "LOCK" try button or the Ctrl-Alt-L short cut does nothing.
More-ever the problem doesn't seem to be limited to screensavers: once the bug is triggered, krunner no longer work (Alt-F2 does nothing), nor do ksysguard (Ctrl-ESC).

This bug may or may not be related to https://bugs.kde.org/show_bug.cgi?id=192137.

I can post the Xsession-errors, but I fail to notice anything relevant.

How can I help triage this bug?

Comment 1 Gilboa Davara 2009-12-13 20:29:46 UTC

Created attachment 39029 [details]
Composite start/stop script

Comment 2 Gilboa Davara 2009-12-13 20:31:00 UTC

(Sorry for the piglish. Bad hair day :))

Comment 3 Martin Flöser 2009-12-13 20:34:29 UTC

Everything you mention is related to krunner. So my fair guess is that krunner dies when compositing is suspended/resumed. Do you see a crash dialog? Can you try to restart krunner and test if it fixes the issue when the problem occurs?

Comment 4 Gilboa Davara 2009-12-14 04:54:51 UTC

Nice catch!
Restarting krunner from konsole indeed solves the problem.

.xsession-errors attached. But I don't see any crash dialog.

Renaming bug.

- Gilboa

Comment 5 Gilboa Davara 2009-12-14 04:56:32 UTC

Created attachment 39039 [details]
xsession errors.

P.S. I'm using the nVidia binary blob. (May, or may not be relevant)

Comment 6 Fredrik Höglund 2009-12-26 16:11:50 UTC

Backtrace from krunner:

Program received signal SIGBUS, Bus error.
0xb6af47b1 in KPixmapCache::Private::mmapFile (this=0x834cf60, filename=..., info=0x834cf90, newsize=33656832)
    at /src/kde4/kdelibs/kdeui/util/kpixmapcache.cpp:482                                                      
482         if(0 == info->indexHeader->size) {                                                                
(gdb) bt                                                                                                      
#0  0xb6af47b1 in KPixmapCache::Private::mmapFile (this=0x834cf60, filename=..., info=0x834cf90, newsize=33656832)
    at /src/kde4/kdelibs/kdeui/util/kpixmapcache.cpp:482
#1  0xb6af6252 in KPixmapCache::Private::mmapFiles (this=0x834cf60) at /src/kde4/kdelibs/kdeui/util/kpixmapcache.cpp:410
#2  0xb6af5f8d in KPixmapCache::Private::init (this=0x834cf60) at /src/kde4/kdelibs/kdeui/util/kpixmapcache.cpp:1046
#3  0xb6af7cb6 in KPixmapCache::discard (this=0x8417b70) at /src/kde4/kdelibs/kdeui/util/kpixmapcache.cpp:1262
#4  0xb6af8330 in KPixmapCache::deleteCache (name=...) at /src/kde4/kdelibs/kdeui/util/kpixmapcache.cpp:1240
#5  0xb6e4b4b4 in Plasma::ThemePrivate::discardCache (this=0x81491e0) at /src/kde4/kdelibs/plasma/theme.cpp:221
#6  0xb6e4b94c in Plasma::ThemePrivate::compositingChanged (this=0x81491e0) at /src/kde4/kdelibs/plasma/theme.cpp:213
#7  0xb6e50fae in Plasma::Theme::qt_metacall (this=0x8137f88, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfffebfc)
    at /src/kde4/kdelibs/build/plasma/theme.moc:108
#8  0xb5c3d305 in QMetaObject::metacall (object=0x188, cl=QMetaObject::InvokeMetaMethod, idx=6, argv=0xbfffebfc)
    at /src/kde4/qt/src/corelib/kernel/qmetaobject.cpp:237
#9  0xb5c4b277 in QMetaObject::activate (sender=0x8144d18, m=0xb6c2aaa0, local_signal_index=0, argv=0xbfffebfc)
    at /src/kde4/qt/src/corelib/kernel/qobject.cpp:3263
#10 0xb6aebf33 in KSelectionWatcher::newOwner (this=0x8144d18, _t1=77594658) at /src/kde4/kdelibs/build/kdeui/kmanagerselection.moc:152
#11 0xb6aec251 in KSelectionWatcher::owner (this=0x8144d18) at /src/kde4/kdelibs/kdeui/util/kmanagerselection.cpp:451                  
#12 0xb6aec2e6 in KSelectionWatcher::filterEvent (this=0x8144d18, ev_P=0x188) at /src/kde4/kdelibs/kdeui/util/kmanagerselection.cpp:468
#13 0xb6aed7e7 in KSelectionWatcher::Private::x11Event (this=0x8144ce8, ev_P=0xbffff0ac)                                               
    at /src/kde4/kdelibs/kdeui/util/kmanagerselection.cpp:395                                                                          
#14 0xb6a666c9 in KAppX11HackWidget::publicx11Event (this=0x8069d18, _event=0xbffff0ac)                                                
    at /src/kde4/kdelibs/kdeui/kernel/kapplication.cpp:903                                                                             
#15 KApplication::x11EventFilter (this=0x8069d18, _event=0xbffff0ac) at /src/kde4/kdelibs/kdeui/kernel/kapplication.cpp:953
#16 0xb615180e in qt_x11EventFilter (ev=0xbffff0ac) at /src/kde4/qt/src/gui/kernel/qapplication_x11.cpp:399
#17 0xb615e0f7 in QApplication::x11ProcessEvent (this=0x8069d18, event=0xbffff0ac)
    at /src/kde4/qt/src/gui/kernel/qapplication_x11.cpp:3231
#18 0xb6187a32 in x11EventSourceDispatch (s=0x80745b0, callback=0, user_data=0x0)
    at /src/kde4/qt/src/gui/kernel/qguieventdispatcher_glib.cpp:146
#19 0xb4d29e98 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#20 0xb4d2d623 in ?? () from /lib/libglib-2.0.so.0
#21 0xb4d2d7a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#22 0xb5c60181 in QEventDispatcherGlib::processEvents (this=0x806a010, flags=...)
    at /src/kde4/qt/src/corelib/kernel/qeventdispatcher_glib.cpp:412
#23 0xb6187255 in QGuiEventDispatcherGlib::processEvents (this=0x806a010, flags=...)
    at /src/kde4/qt/src/gui/kernel/qguieventdispatcher_glib.cpp:204
#24 0xb5c371da in QEventLoop::processEvents (this=0xbffff300, flags=...) at /src/kde4/qt/src/corelib/kernel/qeventloop.cpp:149
#25 0xb5c373a2 in QEventLoop::exec (this=0xbffff300, flags=...) at /src/kde4/qt/src/corelib/kernel/qeventloop.cpp:197
#26 0xb5c39831 in QCoreApplication::exec () at /src/kde4/qt/src/corelib/kernel/qcoreapplication.cpp:981
#27 0xb60dd8f7 in QApplication::exec () at /src/kde4/qt/src/gui/kernel/qapplication.cpp:3572
#28 0xb7fb09f6 in kdemain (argc=2, argv=0xbffff494) at /src/kde4/kdebase/workspace/krunner/main.cpp:65
#29 0x08048792 in main (argc=Cannot access memory at address 0x188
 at /src/kde4/kdebase/workspace/build/krunner/krunner_dummy.cpp:3

*** This bug has been marked as a duplicate of bug 182026 ***