It’s normal if you use the Nvidia proprietary driver. Every notification leaks one fd, so if you get a lot of notifications it’ll segfault once or twice per day.
It is normal for KDE. KDE is mockingly called KrashDE in Linux circles for a reason. We're only 4 days into 2026 and there's already dozens of crash-related bugs filled in the bug tracker: https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_...
Yes, KDE aggressively caches and indexes things by default whenever you have free RAM unless you disable this behavior in multiple places in multiple applications. For example, in Okular you can tune it to choose how much of a pdf you want to keep rendered in memory, if you have a tonne of memory, this makes it the smoothest pdf viewer I have ever used.
It has become reasonable graceful in giving it back when you you need it nowadays.
xobs|1 month ago
This was apparently fixed in version 590 of the driver which was released only recently: https://forums.developer.nvidia.com/t/fd-leak-with-explicit-...
vrighter|1 month ago
cogman10|1 month ago
I've been running plasma for over a year, there was like 1 crash during the 5->6 transition, it's otherwise been perfectly fine.
diath|1 month ago
Even things as basic as handling the wallpapers was crashing users' desktops up until recently: https://www.phoronix.com/news/Plasma-6.5-Crash-Fixes
fooker|1 month ago
Literally any piece of complex software. See LLVM for example. LLVM is the backbone of most compiler work in the world right now.
https://github.com/llvm/llvm-project/issues
marginalia_nu|1 month ago
Does KDE use RAM differently than every other software?
fooker|1 month ago
It has become reasonable graceful in giving it back when you you need it nowadays.