Description of problem: There is a web app I use in Firefox, which triggers some kind of extreme memory leak (~400MB/s). Within a few minutes, my desktop becomes unresponsive and the session is killed by systemd-oomd. In my experience, it may or may not be possible to log back in without rebooting. Dec 21 19:51:30 localhost.localdomain systemd-oomd[3165]: Killed /user.slice/user-1000.slice/user/session.slice/org.gnome.Shell due to memory pressure for /user.slice/user-1000.slice/user being 59.89% > 50.00% for > 20s with reclaim activity Dec 21 19:51:31 localhost.localdomain systemd[4138]: org.gnome.Shell: systemd-oomd killed 14 process(es) in this unit. Version-Release number of selected component (if applicable): systemd.x86_64 249.7-2.fc35 How reproducible: All I need to do is visit the website in question in Firefox, it happens 100% of the time. But there are other possible triggers (see below). Actual results: GNOME session is killed. Expected results: Only Firefox or some subset of processes in my user session are killed. System should remain usable. Not losing all work from unrelated processes. Additional info: I should note, this is not the ONLY scenario in which this occurs. I got the idea to attempt debugging the Firefox leak, with my own build in a VM. Well, long before I can even begin such a build, the GNOME session is killed just the same. It takes longer, but the end result is the same. And I'm certain that if Firefox is simply left running long enough, even without some critical memory leak, my session will also be killed (I've seen this behavior, too). So I think it's not necessarily related to how quickly the memory is consumed.
Interesting. With a clean Fedora 35 install in a VM, the web app in question doesn't cause a leak. So I tried the test on https://fedoraproject.org/wiki/Changes/EnableSystemdOomd In the VM, systemd-oomd kicks in after a few seconds of unresponsiveness and kills the process. On my normal desktop, the system becomes unresponsive for at least 30s. Eventually I regain control, but systemd-oomd never kicked in.
*** Bug 2119028 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.