Version: unspecified (using Devel) OS: Linux After some time, plasma-desktop ate 950 MB of memory. Here is the core dump of it: http://www.morrohun.hu/temp/plasma-core.7z Here is its backtrace from that state: #0 0x00007f9d88ca3d03 in poll () from /lib64/libc.so.6 #1 0x00007f9d871ed91a in _xcb_conn_wait (c=0x68fb10, cond=<value optimized out>, vector=0x0, count=0x0) at xcb_conn.c:306 #2 0x00007f9d871ef2e4 in xcb_wait_for_reply (c=0x68fb10, request=73769202, e=0x7fff0a8d4030) at xcb_in.c:390 #3 0x00007f9d8aa6e213 in _XReply (dpy=0x68b530, rep=0x7fff0a8d4080, extra=0, discard=1) at xcb_io.c:454 #4 0x00007f9d8aa4bbb3 in XGetSelectionOwner (dpy=0x68b530, selection=<value optimized out>) at GetSOwner.c:43 #5 0x00007f9d8b0bfb9c in KWindowSystem::compositingActive () at /usr/src/debug/kdelibs-4.4.85/kdeui/windowmanagement/kwindowsystem_x11.cpp:765 #6 0x00007f9d7af487e1 in PanelView::drawBackground (this=0x7fff0a8d3f20, painter=0x1, rect=...) at /usr/src/debug/kdebase-workspace-4.4.85/plasma/desktop/shell/panelview.cpp:1464 #7 0x00007f9d89a23742 in QGraphicsView::paintEvent (this=<value optimized out>, event=<value optimized out>) at graphicsview/qgraphicsview.cpp:3379 #8 0x00007f9d89456232 in QWidget::event (this=0x1642de0, event=0x7fff0a8d4f20) at kernel/qwidget.cpp:8190 #9 0x00007f9d897dde86 in QFrame::event (this=0x1642de0, e=0x7fff0a8d4f20) at widgets/qframe.cpp:557 #10 0x00007f9d89a1eb8b in QGraphicsView::viewportEvent (this=0x1642de0, event=0x7fff0a8d4f20) at graphicsview/qgraphicsview.cpp:2787 #11 0x00007f9d8a238a87 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<value optimized out>, receiver=0x164d450, event=0x7fff0a8d4f20) at kernel/qcoreapplication.cpp:841 #12 0x00007f9d8940032c in QApplicationPrivate::notify_helper (this=0x6844d0, receiver=0x164d450, e=0x7fff0a8d4f20) at kernel/qapplication.cpp:4298 #13 0x00007f9d8940693b in QApplication::notify (this=0x678c10, receiver=0x164d450, e=0x7fff0a8d4f20) at kernel/qapplication.cpp:4185 #14 0x00007f9d8af87756 in KApplication::notify (this=0x678c10, receiver=0x164d450, event=0x7fff0a8d4f20) at /usr/src/debug/kdelibs-4.4.85/kdeui/kernel/kapplication.cpp:302 #15 0x00007f9d8a23967c in QCoreApplication::notifyInternal (this=0x678c10, receiver=0x164d450, event=0x7fff0a8d4f20) at kernel/qcoreapplication.cpp:726 #16 0x00007f9d8945e81d in sendSpontaneousEvent (event=<value optimized out>, receiver=<value optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:218 #17 QWidgetPrivate::drawWidget (event=<value optimized out>, receiver=<value optimized out>) at kernel/qwidget.cpp:5363 #18 0x00007f9d8945f4b8 in QWidgetPrivate::paintSiblingsRecursive (this=<value optimized out>, pdev=<value optimized out>, siblings=..., index=2, rgn=<value optimized out>, offset=<value optimized out>, flags=4, sharedPainter=0x0, backingStore=0x12f4e20) at kernel/qwidget.cpp:5476 #19 0x00007f9d8945e57a in QWidgetPrivate::drawWidget (this=0x16521f0, pdev=<value optimized out>, rgn=..., offset=<value optimized out>, flags=<value optimized out>, sharedPainter=0x0, backingStore=0x12f4e20) at kernel/qwidget.cpp:5412 #20 0x00007f9d89616c85 in QWidgetBackingStore::sync (this=0x12f4e20) at painting/qbackingstore.cpp:1300 #21 0x00007f9d894501b0 in QWidgetPrivate::syncBackingStore (this=0x16521f0) at kernel/qwidget.cpp:1688 #22 0x00007f9d89456935 in QWidget::event (this=0x1642de0, event=0x282f9b20) at kernel/qwidget.cpp:8337 #23 0x00007f9d897dde86 in QFrame::event (this=0x1642de0, e=0x282f9b20) at widgets/qframe.cpp:557 #24 0x00007f9d8986952b in QAbstractScrollArea::event (this=0x1642de0, e=0x282f9b20) at widgets/qabstractscrollarea.cpp:989 #25 0x00007f9d7af46910 in PanelView::event (this=0x1642de0, event=0x282f9b20) at /usr/src/debug/kdebase-workspace-4.4.85/plasma/desktop/shell/panelview.cpp:1485 #26 0x00007f9d8940035c in QApplicationPrivate::notify_helper (this=0x6844d0, receiver=0x1642de0, e=0x282f9b20) at kernel/qapplication.cpp:4302 #27 0x00007f9d8940693b in QApplication::notify (this=0x678c10, receiver=0x1642de0, e=0x282f9b20) at kernel/qapplication.cpp:4185 #28 0x00007f9d8af87756 in KApplication::notify (this=0x678c10, receiver=0x1642de0, event=0x282f9b20) at /usr/src/debug/kdelibs-4.4.85/kdeui/kernel/kapplication.cpp:302 #29 0x00007f9d8a23967c in QCoreApplication::notifyInternal (this=0x678c10, receiver=0x1642de0, event=0x282f9b20) at kernel/qcoreapplication.cpp:726 #30 0x00007f9d8a23cd34 in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:215 #31 QCoreApplicationPrivate::sendPostedEvents (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.cpp:1367 #32 0x00007f9d89a0b01a in dispatchPendingUpdateRequests (this=<value optimized out>) at ../../src/gui/graphicsview/qgraphicsview_p.h:184 #33 QGraphicsScenePrivate::_q_processDirtyItems (this=<value optimized out>) at graphicsview/qgraphicsscene.cpp:509 #34 0x00007f9d89a0b5a2 in QGraphicsScene::qt_metacall (this=0x819440, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0x1d45c580) at .moc/release-shared/moc_qgraphicsscene.cpp:130 #35 0x00007f9d81e37f95 in Plasma::Corona::qt_metacall (this=0x7fff0a8d3f20, _c=ReadProperty, _id=-1, _a=0xffffffffffffffff) at /usr/src/debug/kdelibs-4.4.85/build/plasma/corona.moc:109 #36 0x00007f9d7af38d85 in DesktopCorona::qt_metacall (this=0x7fff0a8d3f20, _c=ReadProperty, _id=-1, _a=0xffffffffffffffff) at /usr/src/debug/kdebase-workspace-4.4.85/build/plasma/desktop/shell/desktopcorona.moc:101 #37 0x00007f9d8a249489 in QObject::event (this=0x819440, e=0x22929b40) at kernel/qobject.cpp:1240 #38 0x00007f9d89a07550 in QGraphicsScene::event (this=0x819440, event=0x22929b40) at graphicsview/qgraphicsscene.cpp:3501 #39 0x00007f9d8940035c in QApplicationPrivate::notify_helper (this=0x6844d0, receiver=0x819440, e=0x22929b40) at kernel/qapplication.cpp:4302 #40 0x00007f9d8940693b in QApplication::notify (this=0x678c10, receiver=0x819440, e=0x22929b40) at kernel/qapplication.cpp:4185 #41 0x00007f9d8af87756 in KApplication::notify (this=0x678c10, receiver=0x819440, event=0x22929b40) at /usr/src/debug/kdelibs-4.4.85/kdeui/kernel/kapplication.cpp:302 #42 0x00007f9d8a23967c in QCoreApplication::notifyInternal (this=0x678c10, receiver=0x819440, event=0x22929b40) at kernel/qcoreapplication.cpp:726 #43 0x00007f9d8a23cd34 in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:215 #44 QCoreApplicationPrivate::sendPostedEvents (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.cpp:1367 #45 0x00007f9d8a263193 in sendPostedEvents () at kernel/qcoreapplication.h:220 #46 postEventSourceDispatch () at kernel/qeventdispatcher_glib.cpp:276 #47 0x00007f9d85dc7dee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #48 0x00007f9d85dcb7b8 in ?? () from /usr/lib64/libglib-2.0.so.0 #49 0x00007f9d85dcb8e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #50 0x00007f9d8a262cd3 in QEventDispatcherGlib::processEvents (this=0x684240, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412 #51 0x00007f9d894aeb2e in QGuiEventDispatcherGlib::processEvents (this=0x7fff0a8d3f20, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #52 0x00007f9d8a237f92 in QEventLoop::processEvents (this=<value optimized out>, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece. ) at kernel/qeventloop.cpp:149 #53 0x00007f9d8a23836c in QEventLoop::exec (this=0x7fff0a8d6fa0, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece. ) at kernel/qeventloop.cpp:201 #54 0x00007f9d8a23d01b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003 #55 0x00007f9d7af3f016 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.4.85/plasma/desktop/shell/main.cpp:118 #56 0x0000000000407a18 in launch (argc=1, _name=<value optimized out>, args=<value optimized out>, cwd=<value optimized out>, envc=0, envs=<value optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40af1b "0") at /usr/src/debug/kdelibs-4.4.85/kinit/kinit.cpp:723 #57 0x00000000004086d0 in handle_launcher_request (sock=8, who=<value optimized out>) at /usr/src/debug/kdelibs-4.4.85/kinit/kinit.cpp:1215 #58 0x0000000000408b81 in handle_requests (waitForPid=0) at /usr/src/debug/kdelibs-4.4.85/kinit/kinit.cpp:1408 #59 0x0000000000409852 in main (argc=4, argv=<value optimized out>, envp=<value optimized out>) at /usr/src/debug/kdelibs-4.4.85/kinit/kinit.cpp:1892 Reproducible: Didn't try OS: Linux (x86_64) release 2.6.31.12-0.2-desktop Compiler: gcc
Can confirm. After having KDE running through a whole night plasma-desktop ate over 400 MB of memory. Running for the rest of the day increased the consumption to 1,5 GB. Using: Linux 2.6.33-ARCH (x86) KDE 4.5 Beta2
I can confirm, that on my notebook, process "plasma-desktop" ate over 1.2G of RAM a day. I've restart that process and I have same situation next morning.
I had this problem with 4.4.85. Seems to be gone with 4.4.90.
It's 4.5.0 release and plasma is really greedy for memory. In have an hour it's ate over 200 mb. Unbelievable that it's a release.
OS: Arch Linux 64bit uname: Linux uw000459 2.6.34-ARCH #1 SMP PREEMPT Mon Jul 5 22:12:11 CEST 2010 x86_64 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz GenuineIntel GNU/Linux Package version: kdemod-core/kdemod-kdebase 4.5.1-1 Memory leak: after some time starts to consume cca 0.5MB per second until SWAP is 100% filled or until I kill "kdinit4: plasma-desktop" process...
*** This bug has been confirmed by popular vote. ***
KDE 4.6.00 OpenSUSE 11.4 uname: Linux dhcppc0 2.6.37.6-0.7-desktop #1 SMP PREEMPT 2011-07-21 02:17:24 +0200 x86_64 x86_64 x86_64 GNU/Linux I had the same problem: plasma-desktop using insane amounts of memory, over 200MB after a few hours. I had, among others, the Now Playing widget and RSI break widget on my desktop. I removed both and the problem hasn't reoccurred since. If you're using any of these widgets, please try removing them and report the results, if any.
*** This bug has been marked as a duplicate of bug 237837 ***
In this case can I delete the 150 MB core file from its external location?
Since I got no answer whether I can delete the core dump, and there was no advancement resolving this bug since one and a half year, I removed the uploaded core dump.