https://bugs.kde.org/show_bug.cgi?id=361521
--- Comment #14 from Chris Samuel <k...@csamuel.org> --- (In reply to David Edmundson from comment #12) > Large virtual memory isn't a problem. It can just mean we've mapped a file > on disk, even a file that isn't actually that size. We're not using up /any/ > resources by doing it. OK thanks. > If your resident memory size is high, that's a problem (and the 450Mb is > high, that we should identify and fix). Virtual memory being high is pretty > much a non issue until proved otherwise. Here is what ksysguard tells me about the breakdown of actual memory usage. Process 2344 - plasmashell Summary The process plasmashell (with pid 2344) is using approximately 452.1 MB of memory. It is using 447.7 MB privately, and a further 33.5 MB that is, or could be, shared with other programs. Dividing up the shared memory between all the processes sharing that memory we get a reduced shared memory usage of 4.4 MB. Adding that to the private usage, we get the above mentioned total memory footprint of 452.1 MB. Library Usage The memory usage of a process is found by adding up the memory usage of each of its libraries, plus the process's own heap, stack and any other mappings, plus the stack of its 24 threads. Private 435808 KB [heap] 12212 KB /drm mm object (deleted) 1892 KB /home/chris/.cache/plasma_theme_default_v5.25.kcache [etc] So basically it's all heap usage, with the deleted DRM objects contributing just 12MB. All the best, Chris -- You are receiving this mail because: You are watching all bug changes.
