Version: (using Devel) Compiler: gcc 4.3.2 OS: Linux Installed from: Compiled sources I have 4gb of ram, several gigabyte of swap, amd64 system. Current Xorg, KDEsvn, happens with all KDEsvn versions I tried in the last 3 month: click on kickoff, go to the recently used tab, click on one of the apps, but hold the button and drag a bit. For additional fun, click twice or on another app too. In less than a second all of the 4gb of ram are gobbled up by plasma. Before you even can think about popping up konsole to killall -9 plasma you are several hundred megabytes into swap. When you are finally able to switch to a vt - KDE is completly unresponsive and it takes a good minute to do so - and log in (maybe on the second try, because of login timeout), and you dare to do a free -h you are gigabytes into swap. Yes, gigabytes of swap are used up. All of ram is used up. System crawls. Complete swap storm. killall -9 plasma and suddenly you have 3gb of free ram, everything is fine again. Go back to KDE, run krunnner, start plasma and continue where you left.
cannot reproduce (4.1.87) and I've only 256MB RAM on my laptop.
i can't reproduce this one either.
I experience different behaviour: when trying to reproduce this bug, just after releasing mouse button plasma crashes instantly and is restarted.
I've forgot to add: KDE 4.2 Kubuntu packages from backports
reproduced here on mandriva with kde 4.2.0 and like comment #3, plasma directly crashed but before plasma was slow. My distribution is in upgrade to kde 4.2.1 when it will be done i will be able to paste the Kcrash
Here I can reproduce exactly the same behavior described by Volker Hemmann, using KDE 4.2.2 on kubuntu jaunty. I've got a similar system, ~4Gb of RAM, ~5Gb of swap. I noticed this by accident (thanks, synaptics touchpad) and ended here to file a bug report with the exact description provided by Volker.
4.2.2 from Ubuntu packages - still crash instead of memory consumption
2GB RAM, 500 MB swap
@karaluh, @Diego, @Volker, @Nicolas: which Qt, Xorg and video driver version did you use? Thanks.
as you can see from my comment, it was then current svn code. Xorg was 1.5.3 (?). qt must have been 4.4.something. Really - that was 4 month ago. I have updated my system ca 100 times since then...
I can still reproduce it, Kubuntu Jaunty, qt 4.5.0, xserver 1.6.0, fglrx 8.600
those experiencing a crash: please post a backtrace to this report. those for whom it just allocates memory until it stuffs the system: please report your graphics driver and version, qt version _and_ kde version. all three will be required to get a full idea of what the common denominator is. (really, how else can we diagnose a problem we can't reproduce without some details?)
Program: Przestrzeń robocza Plazmy (plasma), sygnał SIGSEGV [Current thread is 0 (LWP 31116)] Thread 3 (Thread 0xa9404b90 (LWP 31306)): #0 0xb80d2430 in __kernel_vsyscall () #1 0xb523b0e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb641e2ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6 #3 0xb660a9b2 in QWaitCondition::wait (this=0x9c0e740, mutex=0x9c0e73c, time=4294967295) at thread/qwaitcondition_unix.cpp:87 #4 0xb7a8c152 in QHostInfoAgent::run (this=0x9c0e730) at kernel/qhostinfo.cpp:260 #5 0xb660996e in QThreadPrivate::start (arg=0x9c0e730) at thread/qthread_unix.cpp:189 #6 0xb52374ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb640f49e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 2 (Thread 0xa8a67b90 (LWP 31315)): #0 0xb80d2430 in __kernel_vsyscall () #1 0xb523b0e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb641e2ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6 #3 0xb660a9b2 in QWaitCondition::wait (this=0x99cf6e0, mutex=0x99cf6dc, time=4294967295) at thread/qwaitcondition_unix.cpp:87 #4 0xa95c7b9a in ?? () from /usr/lib/kde4/plasma_wallpaper_image.so #5 0xb660996e in QThreadPrivate::start (arg=0x9d2ec80) at thread/qthread_unix.cpp:189 #6 0xb52374ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb640f49e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb4d3c710 (LWP 31116)): [KCrash Handler] #6 QAbstractItemModel::decodeData (this=0x9a8d3d0, row=0, column=0, parent=@0xbfbeaed4, stream=@0xbfbead44) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:87 #7 0xb66f73d4 in QAbstractItemModel::dropMimeData (this=0x9a8d3d0, data=0x9c183e8, action=Qt::MoveAction, row=0, column=0, parent=@0xbfbeaed4) at kernel/qabstractitemmodel.cpp:1517 #8 0xb6fc2c75 in QStandardItemModel::dropMimeData (this=0x9a8d3d0, data=0x9c183e8, action=Qt::MoveAction, row=-1, column=-1, parent=@0xbfbeaed4) at itemviews/qstandarditemmodel.cpp:2998 #9 0xb6f214e1 in QAbstractItemView::dropEvent (this=0x9a86548, event=0xbfbeb64c) at itemviews/qabstractitemview.cpp:1844 #10 0xa99054cc in ?? () from /usr/lib/kde4/plasma_applet_launcher.so #11 0xb6a017b1 in QWidget::event (this=0x9a86548, event=0xbfbeb64c) at kernel/qwidget.cpp:7698 #12 0xb6ddbd83 in QFrame::event (this=0x9a86548, e=0xbfbeb64c) at widgets/qframe.cpp:559 #13 0xb6e7bd3f in QAbstractScrollArea::viewportEvent (this=0x9a86548, e=0x74696f6f) at widgets/qabstractscrollarea.cpp:962 #14 0xb6f2da37 in QAbstractItemView::viewportEvent (this=0x9a86548, event=0xbfbeb64c) at itemviews/qabstractitemview.cpp:1466 #15 0xb6e7e345 in QAbstractScrollAreaFilter::eventFilter (this=0x9a8bd40, o=0x9a8f5d0, e=0xbfbeb64c) at widgets/qabstractscrollarea_p.h:100 #16 0xb66fcc5a in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x96ec650, receiver=0x9a8f5d0, event=0xbfbeb64c) at kernel/qcoreapplication.cpp:718 #17 0xb69aaf0a in QApplicationPrivate::notify_helper (this=0x96ec650, receiver=0x9a8f5d0, e=0xbfbeb64c) at kernel/qapplication.cpp:4080 #18 0xb69b3841 in QApplication::notify (this=0x96cebd0, receiver=0x9a8f5d0, e=0xbfbeb64c) at kernel/qapplication.cpp:4037 #19 0xb780394d in KApplication::notify (this=0x96cebd0, receiver=0x9a8f5d0, event=0xbfbeb64c) at /build/buildd/kde4libs-4.2.2/kdeui/kernel/kapplication.cpp:307 #20 0xb66fda3b in QCoreApplication::notifyInternal (this=0x96cebd0, receiver=0x9a8f5d0, event=0xbfbeb64c) at kernel/qcoreapplication.cpp:602 #21 0xb6a305ad in QX11Data::xdndHandleDrop (this=0x96f3c10, xe=0xbfbeb748, passive=false) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #22 0xb6a35233 in QDragManager::drop (this=0x9e48ce8) at kernel/qdnd_x11.cpp:1692 #23 0xb6a353f6 in QDragManager::eventFilter (this=0x9e48ce8, o=0x9f1af90, e=0xbfbebbe8) at kernel/qdnd_x11.cpp:1292 #24 0xb66fcd1c in QCoreApplicationPrivate::sendThroughApplicationEventFilters (this=0x96ec650, receiver=0x9f1af90, event=0xbfbebbe8) at kernel/qcoreapplication.cpp:699 #25 0xb69aaea3 in QApplicationPrivate::notify_helper (this=0x96ec650, receiver=0x9f1af90, e=0xbfbebbe8) at kernel/qapplication.cpp:4059 #26 0xb69b3ba1 in QApplication::notify (this=0x96cebd0, receiver=0x9f1af90, e=0xbfbebbe8) at kernel/qapplication.cpp:3786 #27 0xb780394d in KApplication::notify (this=0x96cebd0, receiver=0x9f1af90, event=0xbfbebbe8) at /build/buildd/kde4libs-4.2.2/kdeui/kernel/kapplication.cpp:307 #28 0xb66fda3b in QCoreApplication::notifyInternal (this=0x96cebd0, receiver=0x9f1af90, event=0xbfbebbe8) at kernel/qcoreapplication.cpp:602 #29 0xb69b2c0e in QApplicationPrivate::sendMouseEvent (receiver=0x9f1af90, event=0xbfbebbe8, alienWidget=0x0, nativeWidget=0x9f1af90, buttonDown=0xb7256200, lastMouseReceiver=@0xb7256204) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #30 0xb6a22a0e in QETWidget::translateMouseEvent (this=0x9f1af90, event=0xbfbec22c) at kernel/qapplication_x11.cpp:4425 #31 0xb6a21d37 in QApplication::x11ProcessEvent (this=0x96cebd0, event=0xbfbec22c) at kernel/qapplication_x11.cpp:3421 #32 0xb6a4ccfa in x11EventSourceDispatch (s=0x96f3368, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #33 0xb5035b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #34 0xb50390eb in ?? () from /usr/lib/libglib-2.0.so.0 #35 0xb5039268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #36 0xb6729438 in QEventDispatcherGlib::processEvents (this=0x96b10f0, flags={i = -1078017048}) at kernel/qeventdispatcher_glib.cpp:323 #37 0xb6a4c3f5 in QGuiEventDispatcherGlib::processEvents (this=0x96b10f0, flags={i = -1078017000}) at kernel/qguieventdispatcher_glib.cpp:202 #38 0xb66fc06a in QEventLoop::processEvents (this=0x9c35fb8, flags={i = -1078016936}) at kernel/qeventloop.cpp:149 #39 0xb66fc4aa in QEventLoop::exec (this=0x9c35fb8, flags={i = -1078016824}) at kernel/qeventloop.cpp:200 #40 0xb6a333a0 in QDragManager::drag (this=0x9e48ce8, o=0x9cb9410) at kernel/qdnd_x11.cpp:1952 #41 0xb69be5ca in QDrag::exec (this=0x9cb9410, supportedActions={i = -1078016572}, defaultDropAction=Qt::IgnoreAction) at kernel/qdrag.cpp:282 #42 0xb6f2bf8c in QAbstractItemView::startDrag (this=0x9a86548, supportedActions={i = -1078016432}) at itemviews/qabstractitemview.cpp:3189 #43 0xa99066fe in ?? () from /usr/lib/kde4/plasma_applet_launcher.so #44 0xb6f28f4d in QAbstractItemView::mouseMoveEvent (this=0xbfbec658, event=0xbfbecf98) at itemviews/qabstractitemview.cpp:1547 #45 0xa9906f8f in ?? () from /usr/lib/kde4/plasma_applet_launcher.so #46 0xb6a01a3d in QWidget::event (this=0x9a86548, event=0xbfbecf98) at kernel/qwidget.cpp:7501 #47 0xb6ddbd83 in QFrame::event (this=0x9a86548, e=0xbfbecf98) at widgets/qframe.cpp:559 #48 0xb6e7bd3f in QAbstractScrollArea::viewportEvent (this=0x9a86548, e=0x74696f6f) at widgets/qabstractscrollarea.cpp:962 #49 0xb6f2da37 in QAbstractItemView::viewportEvent (this=0x9a86548, event=0xbfbecf98) at itemviews/qabstractitemview.cpp:1466 #50 0xb6e7e345 in QAbstractScrollAreaFilter::eventFilter (this=0x9a8bd40, o=0x9a8f5d0, e=0xbfbecf98) at widgets/qabstractscrollarea_p.h:100 #51 0xb66fcc5a in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x96ec650, receiver=0x9a8f5d0, event=0xbfbecf98) at kernel/qcoreapplication.cpp:718 #52 0xb69aaf0a in QApplicationPrivate::notify_helper (this=0x96ec650, receiver=0x9a8f5d0, e=0xbfbecf98) at kernel/qapplication.cpp:4080 #53 0xb69b3ba1 in QApplication::notify (this=0x96cebd0, receiver=0x9a8f5d0, e=0xbfbecf98) at kernel/qapplication.cpp:3786 #54 0xb780394d in KApplication::notify (this=0x96cebd0, receiver=0x9a8f5d0, event=0xbfbecf98) at /build/buildd/kde4libs-4.2.2/kdeui/kernel/kapplication.cpp:307 #55 0xb66fda3b in QCoreApplication::notifyInternal (this=0x96cebd0, receiver=0x9a8f5d0, event=0xbfbecf98) at kernel/qcoreapplication.cpp:602 #56 0xb69b2c0e in QApplicationPrivate::sendMouseEvent (receiver=0x9a8f5d0, event=0xbfbecf98, alienWidget=0x9a8f5d0, nativeWidget=0x9aad7e0, buttonDown=0xb7256200, lastMouseReceiver=@0xb7256204) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #57 0xb6a22a0e in QETWidget::translateMouseEvent (this=0x9aad7e0, event=0xbfbed5dc) at kernel/qapplication_x11.cpp:4425 #58 0xb6a21d37 in QApplication::x11ProcessEvent (this=0x96cebd0, event=0xbfbed5dc) at kernel/qapplication_x11.cpp:3421 #59 0xb6a4ccfa in x11EventSourceDispatch (s=0x96f3368, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #60 0xb5035b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #61 0xb50390eb in ?? () from /usr/lib/libglib-2.0.so.0 #62 0xb5039268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #63 0xb6729438 in QEventDispatcherGlib::processEvents (this=0x96b10f0, flags={i = -1078012008}) at kernel/qeventdispatcher_glib.cpp:323 #64 0xb6a4c3f5 in QGuiEventDispatcherGlib::processEvents (this=0x96b10f0, flags={i = -1078011960}) at kernel/qguieventdispatcher_glib.cpp:202 #65 0xb66fc06a in QEventLoop::processEvents (this=0xbfbed840, flags={i = -1078011896}) at kernel/qeventloop.cpp:149 #66 0xb66fc4aa in QEventLoop::exec (this=0xbfbed840, flags={i = -1078011832}) at kernel/qeventloop.cpp:200 #67 0xb66fe959 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880 #68 0xb69aada7 in QApplication::exec () at kernel/qapplication.cpp:3553 #69 0xb8079b56 in kdemain () from /usr/lib/libkdeinit4_plasma.so #70 0x08048712 in _start ()
when I had the problem it happend with fglrx 8.10, 8.11, 8.12. Xorg was 1.5 qt was 4.4, plasma was from then current svn (over a period from roughly september/october to january). Sometime after that it stopped - but that was with 4.2.X and then current qt-copy. I didn't retry until 4.2.1 which was ok, AFAIR. The problem didn't reappear for me from that point on. 4.2.2 was ok for me. current svn for 4.3 is ok.
@karaluh: what version of KDE and Qt is that from? (kde4-config --version will tell us) @Volker: good to know; hopefully we can confirm that and pin it down to pre-4.2.2
I spoke too early - I just reproduced it. F* Open kmenu. Go to 'recently used' click on one of the apps there and drag it a bit. plasmas memory consumption exploded so hard that my machine was instantly locked up in a swap storm. Hadn't even had a chance to kill it. fglrx: 9.4 kernel: 2.6.28.9+reiser4+tuxonice qt-copy from a few days ago kde svn from a few days ago xorg server: 1.6.1 glibc: 2.9_p20081201-r2 desktop effects turned off. amd64 system, 4gb ram, 24gb swap.
kde4-config --version : Qt: 4.5.0 KDE: 4.2.2 (KDE 4.2.2) kde4-config: 1.0 apt-cache policy libqt4-core : libqt4-core: Installed: 4.5.0-0ubuntu4 Candidate: 4.5.0-0ubuntu4 Version table: *** 4.5.0-0ubuntu4 0 500 http://archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status apt-cache policy kdebase-runtime-bin-kde4 kdebase-runtime-bin-kde4: Installed: 4:4.2.2-0ubuntu1 Candidate: 4:4.2.2-0ubuntu1 Version table: *** 4:4.2.2-0ubuntu1 0 500 http://archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status uname -a: Linux zzzzzz 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux
Qt: 4.5.0 KDE: 4.2.2 (KDE 4.2.2) kde4-config: 1.0
SVN commit 961735 by aseigo: don't start a second "phantom drag"; not sure if this is why has been triggering BR#180640, but that code was obviously wrong and was causing visible functionality bugs in any case. can one of the affected reporters on BR#180640 who use KDE from svn please update kickoff and see if this also fixes their issues for them? CCBUG:180640 M +2 -6 urlitemview.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=961735
ok, I tried emerge'ing kdeplasma-workspace-9999. Sadly that fail, luckily it fails after libkickoff.so was built, so I copied it to /usr/kde/live/lib64 replacing the file there and restarted KDE. After I was logged in again, I started konsole and htop, opened the kmenu, went to the 'recently used' tab, did the drag&doubleclick action... cpu load was instantly at 80% for plasma-desktop. Memory consumption was instantly at 50% (with 4gb ram, 24gb swap) and became worse. Machine locked up in swap storm. Keyboard was unresponsive (like caps lock led did not lid up) Only sysrq worked. It goes down so hard and fast there isn't even time to kill plasma-workspace. So, the bug is not fixed - or I made a mistake.
@Volker: i'm not familiar with the gentoo nomenclature for packages; does -9999 mean "from anonsvn as of right now"? because your posting was only 1:20 after i committed the fix to svn.kde.org and anonsvn lags behind that somewhat .. is it possible to get an svn rev #? or, if you open up workspace/plasma/applets/kicker/ui/urlitem.cpp is there this line: QAbstractItemView::startDrag(supportedActions); in the startDrag method?
it depends - but usually it means 'latest anon cvs/svn/git/whatever' but it depends on the ebuild and the eclass which tree is checked out - and to be honest reading eclasses isn't my favorite pastime... startDrag looks like this: void UrlItemView::startDrag(Qt::DropActions supportedActions) { //kDebug() << "Starting UrlItemView drag with actions" << supportedActions; if (!d->watchedIndexForDrag.isValid()) { return; } QMimeData *mimeData = model()->mimeData(selectionModel()->selectedIndexes()); if (!mimeData || mimeData->text().isNull()) { return; } QDrag *drag = new QDrag(this); drag->setMimeData(mimeData); QModelIndex idx = selectionModel()->selectedIndexes().first(); QIcon icon = idx.data(Qt::DecorationRole).value<QIcon>(); d->draggedRow = idx.row(); drag->setPixmap(icon.pixmap(IconSize(KIconLoader::Desktop))); d->dropRect = QRect(); drag->exec(); }
hmm. ok, since this is completely non-reproducible for us, it must be something specific to the data set, e.g. the recent files and applications. for recent documents, there's a directory `kde4-config --localprefix`/share/apps/RecentDocuments/ that contains .desktop files. for recent applications, they are recorded in `kde4-config --localprefix`/share/config/kickoffrc the RecentDocuments may contain sensitive information (names of files), but if some of you don't mind and could package up those files and send them to me (directly by email is fine aseigo at kde dot org) that might help crack this case.
Hi, you got mail. btw, maybe you don't drag the apps in the recently used apps part not enough? Sometimes it survived a little drag in the past- but it always explodes if I hold it for more then just a tenth of a second or really try to drag it. I am not going to test it right now, because I just had to reboot thanks to the bug ;)
> btw, maybe you don't drag the apps in the recently used apps part not enough? i've been doing everything i possibly can think of to trigger it, and that certainly includes doing more than holding it motionless for a brief fraction of a second. this seriously just doesn't cause any problems here.
Aaron, I've just send you the files you requested.
i tested with 4.3 of karmic, and there is no way i can reproduce this. what is the status of this bug with kde 4.3?
I just reproduced it. kmenu on desktop (so it won't close). Go to recently used. picked up konqueror icon, moved it around a bit, let it drop at a different place than the original one (like one or two above or below). Memory consumption EXPLODED. I have 8gb ram, 24gb swap now. Memory consumption in htop jumped to 56% instantly (!) swap storm started, box locked up. alt+ctrl+backspace would help - but luckily somebody really smart deactivated this super usefull feature (grrrrr), so I had to do magic-sysrq eiub. yes, it is that bad.
I am also able to reproduce it, for me it is crashing. kde 4.3, qt 4.5.2
Crashing here too, i'm also able to reproduce it in ubuntu 9.10 (devel branch). I don't know how useful will be, but I created a bug report in https://bugs.launchpad.net/bugs/419239 as it seems that this is mostly reproducible in Ubuntu.
@Diego: there's someone building from source and a gentoo user who can reproduce. i'm still unable to, however, and really don't see what the issue may be.
I also noticed the plasma-desktop using 700MB of desktop systems memory. I do not know what's causing it but noticed it if I do not restart my computer for a week. I am not using any fancy plasmoids. I saw this happening on my laptop as well and they both have different graphics cards so I think its not related to hardware. Is there a way I can get a debug report of plasma-desktop when gets in 500MB+ state ? or any tools to generate a report which might help the kde developers ?
I think this is probably bug 202889, since the only way to even be able to drag or drop anything inside Recently Used is to use a localized environment. (Well, not anymore. I fixed it tonight)
*** This bug has been marked as a duplicate of bug 202889 ***