https://bugs.kde.org/show_bug.cgi?id=444323
--- Comment #4 from Arjen Hiemstra <ahiems...@heimr.nl> --- So the "memory" column shows the so called "VmPSS" value that is retrieved from `/proc/$pid/smaps_rollup`. Unfortunately this file is not world-readable but only user-readable unlike some of the other files in /proc. This means that when we try to read that file for non-user owned processes, we get an access denied and cannot read that value. Additionally, some processes set a flag that tells the kernel to disallow reading that file, which ends up with the same result. Overall, I'm not really happy with how that value is exposed by the kernel, yet it is the best matching value for actual memory we can get, as it includes both the private memory usage as well as the process' share of the shared memory. So by default we use that column. The column called "Memory" in KSysGuard actually still exists but has been renamed to "Private Memory Usage" as that is what it actually is. That column reads from a file that *is* world readable so if you enable that, you get memory information for other processes as well. -- You are receiving this mail because: You are watching all bug changes.
