8
submitted 2 months ago by kelvie@lemmy.ca to c/kde@lemmy.kde.social

According to nvtop, on both my nvidia and AMD computers, kscreenlocker_greet uses 200-400MB of VRAM while the screen is locked -- doesn't that feel excessive for a simple screen locker (I do realize that it's QML and thus in theory can use as much VRAM as say plasmashell).

This is kind of annoying as I was trying to set up a chatbot using my main desktop while it's idle, and would like that extra 400MB back for a higher context length.

Wasn't sure if this was a bug or just how software is nowadays so I opted to start a discussion rather than finishing filing a bug at bugs.kde.org.

Anyway, anyone know of an alternative screenlocker for kwin_wayland?

I thought I would disable kscreenlocker completely (by setting the screen to never lock?) and use something like swayidle and swaylock, but it doesn't look like kwin supports the wayland extensions required to use swaylock.

you are viewing a single comment's thread
view the rest of the comments
[-] m4m4m4m4@lemmy.world 5 points 2 months ago

I'd be surprised if there was any alternative, to be honest.

I'd file the bug - your case is not common. I run kscreenlocker just fine and it's not such a ram hog here.

[-] kelvie@lemmy.ca 3 points 2 months ago

VRAM or regular RAM? It doesn't use that much regular RAM.

this post was submitted on 23 Sep 2024
8 points (100.0% liked)

KDE

5336 readers
113 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 1 year ago
MODERATORS