[Bug 236166] New: Intensive usage of swap space after a few days continuously uptime

Andreas Pietzowski andreas at pietzowski.de
Mon May 3 14:05:06 BST 2010


https://bugs.kde.org/show_bug.cgi?id=236166

           Summary: Intensive usage of swap space after a few days
                    continuously uptime
           Product: kde
           Version: unspecified
          Platform: Ubuntu Packages
        OS/Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: andreas at pietzowski.de


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.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list