On 22/09/2019 03.58, James Knott wrote:
On 2019-09-21 09:28 PM, David C. Rankin wrote:
On 09/20/2019 08:34 AM, James Knott wrote:
I just noticed something curious. There has been another problem, which requires me to occasionally run the command "kquitapp5 plasmashell && kstart5 plasmashell". When I did that, swap dropped from about 3.6 G to 0.5.
This issue continues and I have not been able to find any app causing it. Swap keeps increasing, even though not all of the memory is being used. After killing and restarting the desktop swap is back to zero. I have tried killing individual apps and while that reduces memory use, it has little effect on swap.
You know that you can use "top" to know precisely what process is using swap? top - 13:28:15 up 5 days, 23:07, 3 users, load average: 0,26, 0,45, 0,55 Tasks: 479 total, 1 running, 477 sleeping, 0 stopped, 1 zombie %Cpu(s): 4,5 us, 1,7 sy, 0,1 ni, 89,0 id, 4,8 wa, 0,0 hi, 0,0 si, 0,0 st KiB Mem : 8161116 total, 2281060 free, 4781372 used, 1098684 buff/cache KiB Swap: 25165820 total, 19922552 free, 5243268 used. 2956448 avail Mem PID USER PR NI VIRT RES SHR SWAP S %CPU %MEM TIME+ COMMAND 4416 vscan 20 0 1086788 31788 4260 720144 S 0,000 0,390 7:54.32 clamd 5716 cer 20 0 4382992 1,080g 78204 351276 S 0,000 13,87 239:22.65 thunderbird-bin 5976 cer 20 0 2959464 434296 66256 278816 S 1,190 5,322 43:59.24 Web Content 5923 cer 20 0 2929708 549964 56144 260172 S 0,893 6,739 34:21.23 Web Content 2347 named 20 0 564224 49152 6000 188388 S 0,000 0,602 0:52.50 named 7639 cer 20 0 3914780 5644 1536 178944 S 0,000 0,069 1:15.20 java 6010 cer 20 0 2829244 588560 117052 170712 S 1,786 7,212 41:14.24 Web Content ******
That all seems to be pointing to one big shell that is filling swap. Is it possible that you may have an old config file (some tag-along from kde4) that might be giving plasma fits? (that's just a guess) If everybody isn't suffering the same gradual slowdown/freeze, then it has to be something unique to your config. I don't know of any quick way to find out what is in the swap file, maybe other can offer something there. If we can find out what data is filling it up, then that would at least point in the right direction. Something like an old screen saver, etc.. that the first part of the generic screen save module sets up and allocates for and then forks waiting on some signal to deallocate that never comes? Or maybe of a second display that is no longer there? Just grasping at straws, but it has to be something that is special about your (and a few others) setup.
No, it was a fresh install of 15.1, not an update. I have no idea what might cause this. I've tried various things, but nothing is consistent. I'm surprised swap is being used, when there's still plenty of RAM available.
That doesn't surprise me. Swap is used precisely to free some ram. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)