Application: plasma-desktop (0.4) KDE Platform Version: 4.8.3 (4.8.3) Qt Version: 4.8.1 Operating System: Linux 3.3.4-3.fc17.i686.PAE i686 Distribution: "Fedora release 17 (Beefy Miracle)" -- Information about the crash: - What I was doing when the application crashed: Nothing... system was idle (just running ktorrent & skype)... - Unusual behavior I noticed: process X overflows memory slowly in few hours before crash... and eating CPU 25-30% few hours before crash... The crash can be reproduced every time. -- Backtrace: Application: Оболочка Plasma (plasma-desktop), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0xb76de7c0 (LWP 1132))] Thread 5 (Thread 0xb34b8b40 (LWP 1133)): #0 g_main_context_prepare (context=context@entry=0xb2b004e0, priority=priority@entry=0xb34b8098) at gmain.c:2813 #1 0x4bfab20f in g_main_context_iterate (context=context@entry=0xb2b004e0, block=block@entry=1, dispatch=dispatch@entry=1, self=<error reading variable: Unhandled dwarf expression opcode 0xfa>) at gmain.c:3103 #2 0x4bfab472 in g_main_context_iteration (context=0xb2b004e0, may_block=1) at gmain.c:3184 #3 0x4166313f in QEventDispatcherGlib::processEvents (this=0xb2b00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x4162f87d in QEventLoop::processEvents (this=this@entry=0xb34b81c8, flags=...) at kernel/qeventloop.cpp:149 #5 0x4162fb79 in QEventLoop::exec (this=0xb34b81c8, flags=...) at kernel/qeventloop.cpp:204 #6 0x41519ddc in QThread::exec (this=0x933db18) at thread/qthread.cpp:501 #7 0x4160da5e in QInotifyFileSystemWatcherEngine::run (this=0x933db18) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x4151d221 in QThreadPrivate::start (arg=0x933db18) at thread/qthread_unix.cpp:298 #9 0x4bd23adf in start_thread (arg=0xb34b8b40) at pthread_create.c:309 #10 0x4bc5755e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133 Thread 4 (Thread 0xad42fb40 (LWP 1134)): #0 0xb7725424 in __kernel_vsyscall () #1 0x4bd2712c in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:172 #2 0x45a16aae in WTF::TCMalloc_PageHeap::scavengerThread (this=this@entry=0x46177d20) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #3 0x45a16af0 in WTF::TCMalloc_PageHeap::runScavengerThread (context=0x46177d20) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #4 0x4bd23adf in start_thread (arg=0xad42fb40) at pthread_create.c:309 #5 0x4bc5755e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133 Thread 3 (Thread 0xaca2ab40 (LWP 1135)): #0 0x4bd69dcd in __GI_clock_gettime (clock_id=1, tp=0xaca29f78) at ../sysdeps/unix/clock_gettime.c:116 #1 0x4157c966 in do_gettime (frac=0xaca29f70, sec=0xaca29f68) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x41663b2f in QTimerInfoList::updateCurrentTime (this=0xaca29ff8) at kernel/qeventdispatcher_unix.cpp:343 #4 0xac1004e0 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 2 (Thread 0xabbadb40 (LWP 1136)): #0 0xb7725424 in __kernel_vsyscall () #1 0x4bd2712c in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:172 #2 0x43e1f4bd in QTWTF::TCMalloc_PageHeap::scavengerThread (this=this@entry=0x43f2dd60) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #3 0x43e1f4f0 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=0x43f2dd60) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #4 0x4bd23adf in start_thread (arg=0xabbadb40) at pthread_create.c:309 #5 0x4bc5755e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133 Thread 1 (Thread 0xb76de7c0 (LWP 1132)): [KCrash Handler] #7 __GI___libc_free (mem=0xffffffff) at malloc.c:2973 #8 0x424b329f in QNativeImage::QNativeImage (this=0xb610ae0, width=371, height=175, format=QImage::Format_ARGB32_Premultiplied, widget=0xffffffff) at image/qnativeimage.cpp:198 #9 0x425e6b22 in QRasterWindowSurface::prepareBuffer (this=0xaaf62a0, format=4294967295, widget=0xffffffff) at painting/qwindowsurface_raster.cpp:439 #10 0x425e6e14 in QRasterWindowSurface::setGeometry (this=0xaaf62a0, rect=...) at painting/qwindowsurface_raster.cpp:354 #11 0x4260655f in QWidgetBackingStore::sync (this=0xaa731e8) at painting/qbackingstore.cpp:1220 #12 0x4240393b in QWidgetPrivate::syncBackingStore (this=0xb682800) at kernel/qwidget.cpp:1891 #13 0x42414572 in QWidget::event (this=0xabce838, event=0xb335338) at kernel/qwidget.cpp:8655 #14 0x423b9fbc in QApplicationPrivate::notify_helper (this=0x8bfe050, receiver=0xabce838, e=0xb335338) at kernel/qapplication.cpp:4554 #15 0x423bebd5 in QApplication::notify (this=0x8bfe050, receiver=0xabce838, e=0xb335338) at kernel/qapplication.cpp:4415 #16 0x42f5d422 in KApplication::notify (this=0x8bd0918, receiver=0xabce838, event=0xb335338) at /usr/src/debug/kdelibs-4.8.3/kdeui/kernel/kapplication.cpp:311 #17 0x41630ade in QCoreApplication::notifyInternal (this=0x8bd0918, receiver=0xabce838, event=0xb335338) at kernel/qcoreapplication.cpp:876 #18 0x41634a85 in sendEvent (event=<optimized out>, receiver=<optimized out>) at kernel/qcoreapplication.h:231 #19 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8ba71e0) at kernel/qcoreapplication.cpp:1500 #20 0x41634d0d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1393 #21 0x41662f95 in sendPostedEvents () at kernel/qcoreapplication.h:236 #22 postEventSourceDispatch (s=s@entry=0x8c03d80) at kernel/qeventdispatcher_glib.cpp:279 #23 0x4bfaaf11 in g_main_dispatch (context=0x8bfebb8) at gmain.c:2515 #24 g_main_context_dispatch (context=context@entry=0x8bfebb8) at gmain.c:3052 #25 0x4bfab390 in g_main_context_iterate (context=context@entry=0x8bfebb8, block=block@entry=1, dispatch=dispatch@entry=1, self=<error reading variable: Unhandled dwarf expression opcode 0xfa>) at gmain.c:3123 #26 0x4bfab472 in g_main_context_iteration (context=0x8bfebb8, may_block=1) at gmain.c:3184 #27 0x41663122 in QEventDispatcherGlib::processEvents (this=0x8ba7d48, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #28 0x4246c5db in QGuiEventDispatcherGlib::processEvents (this=0x8ba7d48, flags=...) at kernel/qguieventdispatcher_glib.cpp:207 #29 0x4162f87d in QEventLoop::processEvents (this=this@entry=0xbfa78fb8, flags=...) at kernel/qeventloop.cpp:149 #30 0x4162fb79 in QEventLoop::exec (this=0xbfa78fb8, flags=...) at kernel/qeventloop.cpp:204 #31 0x41634dbb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #32 0x423b7de5 in QApplication::exec () at kernel/qapplication.cpp:3815 #33 0x41f7e456 in kdemain (argc=1, argv=0xbfa79174) at /usr/src/debug/kde-workspace-4.8.3/plasma/desktop/shell/main.cpp:120 #34 0x0804878c in main (argc=1, argv=0xbfa79174) at /usr/src/debug/kde-workspace-4.8.3/i686-redhat-linux-gnu/plasma/desktop/shell/plasma-desktop_dummy.cpp:3 Reported using DrKonqi
Crash is repeated only after reboot... if not then is no repeating after reloading Plasma... by now... I tried to wait 8 hours with my pc is standby, and no repeat.
Crash has repeated after 22 hours after previous without any rebooting/relogging in... But now kwin has not been reloaded, so all looks ugly & made hard reset...
Created attachment 70959 [details] New crash information added by DrKonqi plasma-desktop (0.4) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1 - What I was doing when the application crashed: Just watched how my PC lagging while X eating 30% CPU & launched only Gmail in Google-chrome... That lagging lasted 2-3 hours before crash... -- Backtrace (Reduced): #8 0x42a8ca91 in QGraphicsWidget::~QGraphicsWidget (this=0xc1bd3a0, __in_chrg=<optimized out>) at graphicsview/qgraphicswidget.cpp:272 #9 0x42a8cce3 in QGraphicsWidget::~QGraphicsWidget (this=0xc1bd3a0, __in_chrg=<optimized out>) at graphicsview/qgraphicswidget.cpp:277 #10 0x42a32b60 in QGraphicsItem::~QGraphicsItem (this=0xc1b8fe0, __in_chrg=<optimized out>) at graphicsview/qgraphicsitem.cpp:1493 #11 0x42a8cb1f in ~QGraphicsObject (this=<optimized out>, __in_chrg=<optimized out>) at ../../src/gui/graphicsview/qgraphicsitem.h:547 #12 QGraphicsWidget::~QGraphicsWidget (this=0xc1b8fd8, __in_chrg=<optimized out>) at graphicsview/qgraphicswidget.cpp:232
Also reported in RH Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=819517
Created attachment 71123 [details] broken textures google-chrome As i said, no matter of been system rebooted or not, crash is repeating always in KDE. In some 10-12 hours. For some few hours before crash system begining to be slow. Google-chrome & other programs has a broken interface (attaching screenshots for this). CPU usage is 30-40% by X process. Memory & swap slowly fills more and more (attaching more screenshots for this). If I leave computer working and go to sleep so see broken unstable KDE at morning. I meen - no windows, no tabs, no plasma, only some error message without WM (kwin) and just hot wind from CPU cooler, so i can't do anything but hard reset. Attaching more files.
Created attachment 71124 [details] Broken textures at all (google-chrome & akregator) This and previous screenshot is about 2-3 hours before plasma crash. I don't know what is going on... what the action changes the situation to this. Because before this all system works fine, CPU runs on 5-12%, programs has no broken textures in workspace...
Created attachment 71125 [details] This is what krunner shows on fresh startes system
Created attachment 71126 [details] This is what krunner shows on 1 hour after some strange changes. After 10 hours after fresh start and 1-2 hours before crash. I don't know what is that...
Forgot some note... When this strange action lasts and google-crome (and almost any app) has broken textures inside workspace, firefox has no any problem. It has no broken textures inside workspace and I can use it forward before memory overfills and KDE crashes.
See also: https://bugzilla.redhat.com/show_bug.cgi?id=819517 I launched that report too... and posted some new info in there
I found a source of problem... It was knemo... i just removed it fully (yum remove knemo) and restarted system... now have no problem during 24 hours online =)
OK, triaging to knemo component
That seems odd. Would you please attach your knemorc file? Also, what version of KNemo are you using?
Hrm, seems fedora's pkg maintainer built knemo with -DLEGACY_TRAY_ICON=true to workaround bug #226650 (which has since been fixed for quite awhile). I bet that may be contributing to the problem.
Created attachment 72417 [details] the last knemorc file that been used Included knemorc file... But listen, it's not old file... I just made fresh install of my system few days ago and now it is Fedora 17 x86_64. So i can't tell you what a version of knemo i was used before reinstalling. But in fresh system it was some 0.7.x version. Don't remember what version exactly because i removed fully it 2 days ago (when found problem). But official repos offers 0.7.3-1 now... Yes, i can try version you offered (http://koji.fedoraproject.org/koji/taskinfo?taskID=4228559)... But only if you tell me how to use it. Because i see that it is SRC version of rpm package.
(In reply to comment #14) > Hrm, seems fedora's pkg maintainer built knemo with > -DLEGACY_TRAY_ICON=true > to workaround bug #226650 (which has since been fixed for quite awhile). I > bet that may be contributing to the problem. When KNemo window opened from tray it still can appear on background of other windows without -DLEGACY_TRAY_ICON=true. And I saw such behavior also for other apps.
(In reply to comment #14) > Hrm, seems fedora's pkg maintainer built knemo with > -DLEGACY_TRAY_ICON=true > to workaround bug #226650 (which has since been fixed for quite awhile). I > bet that may be contributing to the problem. Is it (http://kojipkgs.fedoraproject.org//work/tasks/8560/4228560/knemo-0.7.3-1.fc17.1.x86_64.rpm) package that you meen me to try?
that's the one (assuming you're on a x86_64 box)
I just tried this package... 25 hours gone and no same problems found... only 1 time - there was Segmentation Fault (11) by Plasma-desktop... on 20 hour of standby...
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I will be closing this bug.