It would be a problem if I left it on this long regularly, and indeed it is a problem at the moment because I need to leave it on and at this rate I'll be using swap space to do actual work tomorrow just because it's powered on, which will be slow and wear out the SSD that my swap space has to be on (not ideal I know).
My swap is meant to be for an emergency, not because some leaky code in a driver/the kernel/whatever is somehow managing to use 20gb of ram. I can definitely see it being a problem on a low memory system or in other real use cases, so yes it's worth tracking down and fixing to me. Even if it doesn't affect my use case, I still want to fix it for the other people running this distro/kernel/driver/whatever the problem is. As far as I have seen, read, and experienced with other systems, this kind of memory use considering the workload is not normal, and is honestly not acceptable - I have a raspberry pi that has run for several months without a reboot with no noticeable memory leakage/weirdness at all. Imagine if servers behaved like this. NB: logging out and back in also changes nothing, just tried that too. Hamish On 10 Sep 2020, at 22:53, Keith Edmunds <k...@midnighthax.com<mailto:k...@midnighthax.com>> wrote: On Thu, 10 Sep 2020 22:01:20 +0100, hamis...@live.co.uk said: but [...] using 20GB of RAM with almost nothing open [...] is not good behaviour Why not? Is there an actual problem in the day to day use of the system? Or is the problem that you've seen some numbers you don't like the look of / don't understand? -- Next meeting: Online, Jitsi, Tuesday, 2020-10-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
