le9-patch VS sway

Also, are you using a stock kernel? Try using this patchset https://github.com/hakavlad/le9-patch and more specifically set this

This kernel patch work really well: https://github.com/hakavlad/le9-patch/

Oh that’s a known problem. There are many patch sets floating around that fix it by triggering the OOM killer when the system is thrashing: https://github.com/hakavlad/le9-patch

I’ve never ran into this specific problem back when I was daily driving desktop Linux, but I did run into 1000 similar ones that needed bandaid solutions. It’s death of a thousand cuts: https://news.ycombinator.com/item?id=28490753

I actually do use the Zen kernel already. If you are already using the zen kernel , make sure to use the latest one which has le9 patches , imho this patch can Improve user experience in tight memory situations. Check this https://github.com/hakavlad/le9-patch, saw many people praise this , but ymmv. Best of luck

- Limit the amount of thrashing or protect some pages from being reclaimed. This has been proposed by Google first and several other people since then, but AFAIK it has never been implemented in the mainline kernel.

Regarding the latter solution, there is a patchset called le9-patch[1] that is included in some alternative Linux kernels and it should be relatively safe to use.

[1]: https://github.com/hakavlad/le9-patch

Patch i was talking about le9-patch. it's only a proof of concept with very rough edges, but consider it isn't written by an experienced kernel developer with deep knowledge of memory subsystem.

This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.

I also have crashes on sway, but there’s a rough workaround now which prevents the issue totally.

I believe there’s a design issue with Firefox and GTK handling input events; some Wayland compositors have workarounds but others do not.

https://github.com/swaywm/sway/issues/7645

https://bugzilla.mozilla.org/show_bug.cgi?id=1743144

Firefox is my preferred browser and I hope we can keep its engine alive in this era of Chrome dominance.

I'm seeing this: https://github.com/swaywm/sway/wiki/Setting-Environmental-Variables but I haven't figured out how to make GDM do it, and I was wondering if there was a super simple "HEY SWAY READ MY .PROFILE" thing I could do.

So I searched around and found the following bug report where this problem and a possible solution was borough up: https://github.com/swaywm/sway/issues/2966 , which was then immediately closed again.

I've been using Sway since late 2019. I like the workflow of a WM. I honestly find it hard to go back to a DE, I like having a minimalistic desktop.

Sway is fast, minimal, and flexible. Their recommended tools/addons are worth a look: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway

From that list I use greetd + tuigreet as my login manager, sway-launcher-desktop for FZF-powered app launching, and wob for lightweight brightness and volume display (send '50' to the wob socket and it'll show 50%; it doesn't get simpler).