Description of problem:
So, I came back to my workstation today to start my work day. I was surprised to find that all my konsole windows that I had left open the previous day had mysteriously vanished. After lots of intervestigation, I discovered that systemd-omg had snuck in after midnight and murdered them. This was the only evidence left behind:
Jun 22 01:44:09 nuclearis3.gtech systemd-oomd[2755]: Killed /user.slice/user-1000.slice/user/app.slice/app-org.kde.konsole-0aa05c341ada4325b46b1791f3441295.scope due to swap used (7731081216) / total (8589930496) being more than 90.00%
This is problematic, because available memory , as shown by free -h, was above 10 GiB throughout the entire ordeal.
Version-Release number of selected component (if applicable):
systemd-248-2.fc34.x86_64
How reproducible:
Intermittent. This is the second time I've noticed it in 30 days.
Steps to Reproduce:
1. Launch lots of Konsole windows
2. Launch a background task that malloc()s and free()s large amounts of memory, but well within the available system memory.
3. Return the next day
Actual results:
Oooh, noo, where's all my windows?
Expected results:
Everything is like I left it.
Additional info:
System has 32 GiB of RAM. Plenty good for the programs I go out with.
I will work on a patch to check available that available memory is also below a threshold before doing a swap-based kill. I received a separate report about this as well and there are a few situations where things tend to stick around in swap instead of going back to memory.