https://bugs.kde.org/show_bug.cgi?id=505240
--- Comment #48 from Robin Laing <[email protected]> --- I changed my system configuration 2 days ago. Switched from SDDM to GDM which has helped save session issues, so I cannot honestly comment on this bug anymore. Since I made the change, I am feeling that much of the lockup issues are related to sddm and how it calls kwin. I won't be able to do any testing of this installation for a few days. What I found out before is kwin starts acting up when the GPU ram is getting used up. System becomes very unresponsive. It doesn't need to be 100% but high usage. When I tried to switch user, the system would move to a crawl and that is when I came in to report the issue. Since that point, I have found that kscreenlocker_greet is using up 196MiB for the locked session when I open a second session. It is presently the largest GPU usage at 10%. Followed by an open Thunderbird session and then Plasmashell. This is using nvtop to monitor. If I lock my second session, kscreenlocker_greet for the second session uses up about the same amount of GPU ram. I used to be able to open 3 responsive sessions with F41. Now I am limited to 2 sessions, even if I close off most apps. -- You are receiving this mail because: You are watching all bug changes.
