Version: (using KDE 4.4.2) Installed from: Ubuntu Packages First I thought it was my incremental update with old ubuntu versions and all those many of updates to KDE 4.4.2 from backports etc. Now I cleanly installed Kubuntu 10.04 and recognize the same behavior: When I boot my machine and log into KDE everything is fine but when I stay logged in for about two or three days my swap space is eaten up from some KDE based applications. When I run "top" from the commandline I get the following: VIRT RES SHR S %CPU %MEM TIME+ SWAP COMMAND 1295m 79m 16m S 10 1.3 7:08.16 1.2g amarok 1043m 231m 37m S 8 3.9 12:13.76 811m kdevelop.bin 761m 39m 14m S 3 0.7 92:34.17 721m kwin 471m 276m 2904 S 2 4.6 109:22.15 194m Xorg 890m 82m 29m S 1 1.4 0:04.61 807m plasma-desktop 314m 19m 8968 S 1 0.3 0:11.52 295m yakuake What could be the reason for this behavior? Actually I would post this as a bug because I have enough RAM for everything I run but my system really slows down. When I logout and log in again everything is snappy again within the new KDE session.
Sorry, I wanted to say "Actually I would NOT post this as a bug because I have enough RAM ..."
This is still the case with KDE 4.4.4. Isn't there someone out there who has the same issue? Does everybody shut down KDE in the evening and rebooting in the morning? This issue only appears after a few days of continuously running. Is there a way how I can profile that SWAP space?
*** Bug 230825 has been marked as a duplicate of this bug. ***
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!
Dear Bug Submitter, This is a reminder that 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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
No response; assuming it was fixed since then.