this is the first time in many years of my GNU/Linux journey that I saw a BSOD. on my office machine BTW. personal machine has never crashed even once.
the crash was due to 100% RAM and swap usage.
image description:
a mobile-clicked photo of a laptop screen. the background is full black with a sad computer image in the middle. the text below it reads: “Oh no! something has gone wrong. A problem has occurred and the system can’t recover. Please log out and try again.”
just below it is a small button with the text “log out”
Same, what usually spikes yours to 100%?
Up until yesterday I would’ve said “Firefox” (because I hoard tabs), but it turns the real answer was “Firefox running as a Snap.”
(A failed update screwed up my Snap installation, which finally gave me the kick I needed to quit procrastinating and excise it from my system once and for all. I’m running Firefox installed via apt package from Mozilla’s PPA, and now – with the same number of tabs open – my system is hovering around 8 GB memory usage, when before it was constantly bouncing off the 32 GB redline.)
Firefox somewhat regularly crashes or freezes up my laptop (16Gb) due to memory usage and I’m running the default Arch package. I ended up installing a memory watchdog that kills processes when they start using too much. Although I do hoard tabs.
I mean there is a kernel OOM killer and a systemd service that acts well before that. Do you not use systemd?
I do use systemd. I pretty much run stock EndeavorOS
Carelessly running too many programs and not having much RAM.
When I get my Framework 16, I’ll either get 64 or 128GBs of RAM. It’s so cheap nowadays, the only thing stopping me from getting more is simply the increased time to go to sleep and wake up.