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.

▲

marginalia_nu 3 days ago | parent [-]

The Linux kernel does this too, yet it does not crash like KDE. At any given moment, most of your free RAM is used to cache stuff by the kernel, unless you've recently rebooted.

▲

fooker 3 days ago | parent [-]

No, what the Linux kernel does instead is randomly kill user processes :)

It's kinda infamous for that, and had held up Linux adoption for a decade or so.

But you sort of missed the point, I think. The comment chain was about speculating why KDE could possibly crash if there was faulty RAM while other software would be fine. And the kernel absolutely crashes when there's faulty ram.

	▲	marginalia_nu 3 days ago \| parent [-]
		Right, yet it's KDE that is crashing with extreme regularity, and never the kernel.