https://bugs.kde.org/show_bug.cgi?id=505240
--- Comment #52 from Robin Laing <[email protected]> --- A few days later. I am still under the impression that kwin_wayland is an issue but kscreenlocker it worse. Presently, on my system A session that is open and locked, kscreenlocker is using 228MiB of video ram using nvtop. kwin_wayland is using 222MiB of vram. Firefox with over 1000 tabs is at 187MiB. Second account open is running java apps. kwin_wayland for that account is only using 31MiB. I cannot understand why kscreenlocker needs so much vram when the display isn't even being on. Background is a solid colour, don't even have the clock display. This is an strace of the kscreenlocker process. No clock with the display but lots of localtime calls. ppoll([{fd=4, events=POLLIN}, {fd=6, events=POLLIN}, {fd=40, events=POLLIN}, {fd=45, events=POLLIN}, {fd=47, events=POLLIN}, {fd=48, events=POLLIN}, {fd=288, events=POLLIN}], 7, {tv_sec=0, tv_nsec=999000000}, NULL, 8) = 0 (Timeout) newfstatat(AT_FDCWD, "/etc/localtime", {st_mode=S_IFREG|0644, st_size=2332, ...}, 0) = 0 newfstatat(AT_FDCWD, "/etc/localtime", {st_mode=S_IFREG|0644, st_size=2332, ...}, 0) = 0 newfstatat(AT_FDCWD, "/etc/localtime", {st_mode=S_IFREG|0644, st_size=2332, ...}, 0) = 0 newfstatat(AT_FDCWD, "/etc/localtime", {st_mode=S_IFREG|0644, st_size=2332, ...}, 0) = 0 newfstatat(AT_FDCWD, "/etc/localtime", {st_mode=S_IFREG|0644, st_size=2332, ...}, 0) = 0 newfstatat(AT_FDCWD, "/etc/localtime", {st_mode=S_IFREG|0644, st_size=2332, ...}, 0) = 0 newfstatat(AT_FDCWD, "/etc/localtime", {st_mode=S_IFREG|0644, st_size=2332, ...}, 0) = 0 newfstatat(AT_FDCWD, "/etc/localtime", {st_mode=S_IFREG|0644, st_size=2332, ...}, 0) = 0 ppoll([{fd=4, events=POLLIN}, {fd=6, events=POLLIN}, {fd=40, events=POLLIN}, {fd=45, events=POLLIN}, {fd=47, events=POLLIN}, {fd=48, events=POLLIN}, {fd=288, events=POLLIN}], 7, {tv_sec=0, tv_nsec=0}, NULL, 8) = 0 (Timeout) An strace of kwin_wayland is very busy. Video ram was an issue for my problems. Before Wayland, I could have multiple accounts open on this computer and the old video card. Will have to look at kscreenlocker for any bugs. With an nvdia video card, looking at the ram usage is important. I am starting to feel that Wayland requires much more vram than X did. FWIW, checking, via ssh, a machine that has gone into monitor off mode and only one account open. kscreenlocker is using 286MiB . kwin_wayland is only using 123MiB. Plasmashell is at 148MiB. One account open and locked with monitors off and the Vram usage is still 1.58G Of course, there are multiple firefox windows open. One of the large memory usage items is /usr/bin/maliit-keyboard which is almost as much as firefox. If there is anything that I can test, please request and may require details on how to test. -- You are receiving this mail because: You are watching all bug changes.
