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”

  • SteveTech@programming.devEnglish
    2·
    5 months ago

    The cool part is, the kernel and most of the user space is still running fine, so there’s no restart required (although I would anyway), it’s just gnome is having issues.

    I’ve had dodgy hardware cause a kernel panic, which is much more equivalent to a Windows BSOD.

  • OsrsNeedsF2P@lemmy.ml
    1·
    5 months ago

    100% RAM is a huge pain on Linux. I have a widget in my taskbar that always shows my RAM usage so I can tell if I’m about to get doinked

    • exu@feditown.comEnglish
      1·
      4 months ago

      There are automated memory killers that should avoid this. I’m using nohang, but systemd also has some module for this.

      • grue@lemmy.worldEnglish
        1·
        5 months ago

        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.)