Description of problem:
systemd-oomd kills Gnome session on Fedora (35, 36) because it detects lack of memory. In this case it's nothing different from shutting down the computer. It's not what I'd expect from "help utility" to do. If I see nothing moves or any other problem with memory, I know how to shut down my laptop, I don't need a tool to do it in random moment for me. And probably I just close one or two not necessary memory-eating programs, instead of throwing my laptop to wall.
Version-Release number of selected component (if applicable):
Suffering from F34.
How reproducible:
Just work in your normal, code something in VSCode and open a Chrome browser, in some random moment WITHOUT ANY WARNING you'll see the blank screen. Congrats, all you worked on just gone. Is it an implementation of "blue screen" for Fedora? When we talked about features parity between Windows and Fedora, we didn't mean that feature exactly!
Steps to Reproduce:
1. Install Fedora on your workstation.
2. Work for the company.
3. Suffer.
How to survive?
1. DO NOT use cgroups based killing. It just doesn't make any sense on workstation, it's for servers. Just DO NOT.
2. Please tell me that you are going to explode and kill everything with fire, let me decide if I want to shut down the laptop and go drink coffee, or maybe I'll close this Youtube tutorial how to stop oomd killer and it will be back to normal. TALK, don't be silent! Sharing is caring.
3. DO NOT kill Gnome session, JUST DO NOT IN ANY CASE. It doesn't make any sense to continue without it. Just DO NOT. Isn't that easy?
Additional info:
$ free -g
total used free shared buff/cache available
Mem: 30 7 8 3 14 19
Swap: 7 1 6
Isn't it enough for just browsing and coding? Why should the workstation be shut down???
Aug 17 12:40:20 sshnaidm.remote systemd-oomd[1783]: Killed /user.slice/user-1000.slice/user/session.slice/org.gnome.Shell due to memory used (32942882816) / total (33280045056) and swap used (7734882304) / total (8589930496) being more than 90.00%
Description of problem: systemd-oomd kills Gnome session on Fedora (35, 36) because it detects lack of memory. In this case it's nothing different from shutting down the computer. It's not what I'd expect from "help utility" to do. If I see nothing moves or any other problem with memory, I know how to shut down my laptop, I don't need a tool to do it in random moment for me. And probably I just close one or two not necessary memory-eating programs, instead of throwing my laptop to wall. Version-Release number of selected component (if applicable): Suffering from F34. How reproducible: Just work in your normal, code something in VSCode and open a Chrome browser, in some random moment WITHOUT ANY WARNING you'll see the blank screen. Congrats, all you worked on just gone. Is it an implementation of "blue screen" for Fedora? When we talked about features parity between Windows and Fedora, we didn't mean that feature exactly! Steps to Reproduce: 1. Install Fedora on your workstation. 2. Work for the company. 3. Suffer. How to survive? 1. DO NOT use cgroups based killing. It just doesn't make any sense on workstation, it's for servers. Just DO NOT. 2. Please tell me that you are going to explode and kill everything with fire, let me decide if I want to shut down the laptop and go drink coffee, or maybe I'll close this Youtube tutorial how to stop oomd killer and it will be back to normal. TALK, don't be silent! Sharing is caring. 3. DO NOT kill Gnome session, JUST DO NOT IN ANY CASE. It doesn't make any sense to continue without it. Just DO NOT. Isn't that easy? Additional info: $ free -g total used free shared buff/cache available Mem: 30 7 8 3 14 19 Swap: 7 1 6 Isn't it enough for just browsing and coding? Why should the workstation be shut down??? Aug 17 12:40:20 sshnaidm.remote systemd-oomd[1783]: Killed /user.slice/user-1000.slice/user/session.slice/org.gnome.Shell due to memory used (32942882816) / total (33280045056) and swap used (7734882304) / total (8589930496) being more than 90.00%