XMousePasteBlock VS earlyoom

I've actually been using XMousePasteBlock since it does things more elegantly than running an endless loop in the background. But it's still a workaround that shouldn't be necessary unfortunately.

Also, don't run this incredibly bad bash script for purging the X11 selection buffer. Use XMousePasteBlock: https://github.com/milaq/XMousePasteBlock

This is what I use on X11, but I doubt it would work on Wayland. Might be worth trying anyway: https://github.com/milaq/XMousePasteBlock

here go: https://github.com/milaq/XMousePasteBlock

I'm pretty sure I used https://github.com/milaq/XMousePasteBlock, never had to deal with it since

The option to turn it off only works on GTK apps. Here you have a workaround for this. I've been using it for quite some time now and works great so far (I'm on Pop btw).

cp ff gtk em xmp ta km tb ext

This tool named XMousePasteBlock may help you, and it has an AUR package if you use ArchLinux.

> The system is not supposed to 'lock up' when you run out of physical RAM. If it does, something is wrong. It might become slower as pages are flushed to disk but it shouldn't be terrible unless you are really constrained and thrashing. If the Kernel still can't allocate memory, you should expect the OOMKiller to start removing processes. It should not just 'lock up'. Something is wrong.

I don't why but locking up is my usual experience for Desktop Linux for many years and distros, and I remember seeing at least one article explaining why. The only real solution is calling the OOMKiller early either with a daemon or SysRq.

> It should not take minutes. Should happen really quickly once thresholds are reached and allocations are attempted. What is probably happening is that the system has not run out of memory just yet but it is very close and is busy thrashing the swap. If this is happening frequently you may need to adjust your settings (vm.overcommit, vm.admin_reserve_kbytes, etc). Or even deploy something like EarlyOOM (https://github.com/rfjakob/earlyoom). Or you might just need more RAM, honestly.

Yeah. Exactly. But as the thread says, why aren't those things set up automatically?

It's not that simple: some defaults may differ, and some features may arrive at different times (if ever). For example, earlyoom has been enabled on Workstation since F32, but the KDE Plasma spin got it one release later.

Most answers will answer your question, but you can do better and avoid the freezes in the first place. IME almost every time the system froze up and didn't come back in a few seconds it was out of memory. The obvious solution is to add memory, but you can use Early OOM to kill hungry processes if you're running out of memory instead.

It sounds like you're running out of memory though, so if your OS's OOM killer isn't working as well as it should, you can try earlyoom as an alternative.

Swap is indeed supposed to prevent this AFAIK. You can though try some tools like EarlyOOM and see if it helps : https://github.com/rfjakob/earlyoom