Bug 257246

Summary: Kwin crashes [remove, QCache<QString, QPixmap>::insert, KImageCache::insertPixmap, Plasma::ThemePrivate::scheduledCacheUpdate]
Product: [Unmaintained] kdelibs Reporter: Francesco <iozzi>
Component: kshareddatacacheAssignee: kdelibs bugs <kdelibs-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash CC: mpyne, tmax26
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Francesco 2010-11-18 14:38:21 UTC
Application: kwin (4.5.3 (KDE 4.5.3))
KDE Platform Version: 4.5.3 (KDE 4.5.3)
Qt Version: 4.7.0
Operating System: Linux 2.6.36-020636-generic x86_64
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed:
It happened when i tried to open virtualbox while firefox, zimbra and mysql administratore were opened

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f19409097a0 (LWP 1847))]

Thread 2 (Thread 0x7f191c1a7710 (LWP 1860)):
#0  0x00007f19401852e3 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f19409097a0 (LWP 1847)):
[KCrash Handler]
#6  0x00007f193fd02b82 in unlink (this=0xc35818, akey=..., aobject=0x39e1c20, acost=3753) at /usr/include/qt4/QtCore/qcache.h:75
#7  remove (this=0xc35818, akey=..., aobject=0x39e1c20, acost=3753) at /usr/include/qt4/QtCore/qcache.h:161
#8  QCache<QString, QPixmap>::insert (this=0xc35818, akey=..., aobject=0x39e1c20, acost=3753) at /usr/include/qt4/QtCore/qcache.h:183
#9  0x00007f193fd0245d in KImageCache::insertPixmap (this=0xc3e370, key=..., pixmap=...) at ../../kdeui/util/kimagecache.cpp:98
#10 0x00007f193f7222f2 in Plasma::ThemePrivate::scheduledCacheUpdate (this=0xc33fd0) at ../../plasma/theme.cpp:272
#11 0x00007f193f725ebc in Plasma::Theme::qt_metacall (this=0xbe4870, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff8e25a180) at ./theme.moc:119
#12 0x00007f193c9b5b27 in QMetaObject::activate (sender=0xc3c1f0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x206c0) at kernel/qobject.cpp:3280
#13 0x00007f193c9af8f9 in QObject::event (this=0xc3c1f0, e=0x0) at kernel/qobject.cpp:1183
#14 0x00007f193bae7fdc in QApplicationPrivate::notify_helper (this=0xb2b5d0, receiver=0xc3c1f0, e=0x7fff8e25a8d0) at kernel/qapplication.cpp:4396
#15 0x00007f193baedaed in QApplication::notify (this=0x7fff8e25acc0, receiver=0xc3c1f0, e=0x7fff8e25a8d0) at kernel/qapplication.cpp:4277
#16 0x00007f193fc88526 in KApplication::notify (this=0x7fff8e25acc0, receiver=0xc3c1f0, event=0x7fff8e25a8d0) at ../../kdeui/kernel/kapplication.cpp:310
#17 0x00007f193c99dcdc in QCoreApplication::notifyInternal (this=0x7fff8e25acc0, receiver=0xc3c1f0, event=0x7fff8e25a8d0) at kernel/qcoreapplication.cpp:732
#18 0x00007f193c9cd6f2 in sendEvent (this=0xb2bfe0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0xb2bfe0) at kernel/qeventdispatcher_unix.cpp:602
#20 0x00007f193c9cd82c in QEventDispatcherUNIX::processEvents (this=0xb07da0, flags=) at kernel/qeventdispatcher_unix.cpp:923
#21 0x00007f193bb9bc2f in QEventDispatcherX11::processEvents (this=<value optimized out>, flags=) at kernel/qeventdispatcher_x11.cpp:152
#22 0x00007f193c99ca02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#23 0x00007f193c99cdec in QEventLoop::exec (this=0x7fff8e25ac00, flags=) at kernel/qeventloop.cpp:201
#24 0x00007f193c9a0ebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#25 0x00007f194047bf9d in kdemain (argc=<value optimized out>, argv=<value optimized out>) at ../../kwin/main.cpp:531
#26 0x00007f19400c4d8e in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff8e25b2c8) at libc-start.c:226
#27 0x0000000000400669 in _start ()

Reported using DrKonqi
Comment 1 Martin Flöser 2011-07-28 17:25:13 UTC
*** Bug 278719 has been marked as a duplicate of this bug. ***
Comment 2 Andrew Crouthamel 2018-10-29 22:39:03 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-11-13 14:28:56 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
mark the bug 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 4 Bug Janitor Service 2018-11-28 04:57:36 UTC
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!