earlyoom VS flameshot

> 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

I'm using flameshot ( https://flameshot.org/ ), which sounds pretty similar, but FOSS and cross platform.

For your screenshots simply use Flameshot: https://flameshot.org

First, conceptually this is what I mean: think about when using a good screen-capture/annotation tool like flameshot: you select a region of the screen, and "magic" you can "edit" it, "in situ". No, what I'm talking about wouldn't share any of the same technical underpinnings with the way flameshot works, it would be the live monitor output, not a raster dump of the screen made to look like it's live. And the annotating would be done on a different screen. But as a user, this is pretty similar.

Flameshot is a free and open-source screenshot tool for Linux that allows users to take screenshots of an area, a window or the full screen. It then provides an editor where users can modify the screenshots by drawing on them, adding text, highlighting areas, blurring parts and more. Users can save the screenshots in common image formats like PNG and JPEG, and upload them directly to image hosting sites like Imgur.

I would recommend Flameshot, available on Linux, Windows and Mac.

This https://github.com/flameshot-org/flameshot/issues/1529 mat or may not be an issue for you with Flameshot, but it may be for others. It's solvable if it is an issue by using mandatory access control such as AppArmor or conditional build. Just FYI.

Flameshot viene con todo eso.

[3] https://github.com/flameshot-org/flameshot/issues/2848