Not exactly the kind of respect it would like to get - eviltoast

Not exactly as funny meme as I would like it to be, but I just found out about that feature after having to hold the power button due to a frozen system countless times, and I had to tell someone.

    • boredsquirrel@slrpnk.net
      link
      fedilink
      arrow-up
      15
      ·
      edit-2
      6 months ago

      This is great! Why doesnt distros use this by default???

      Just put plasmashell and a few in there and you will have a working oom killer. Finally.

      I will install this the first thing tomorrow

      Wait… Fedora has this since quite a while, strange.

          • mexicancartel@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            9
            ·
            6 months ago

            Not niche there can be times when you want to run something heavy and it auto kills the exact thing you are trying to run. You have a 1gb ram device and it kills everything? Thats undesirable

            • boredsquirrel@slrpnk.net
              link
              fedilink
              arrow-up
              1
              ·
              6 months ago

              Hm… the process itself should not take that much RAM. I dont know if normally the OS should assign the max RAM to the program.

              But this should not happen and I wonder how “just letting it freeze” works

              • mexicancartel@lemmy.dbzer0.com
                link
                fedilink
                English
                arrow-up
                3
                ·
                6 months ago

                It makes system unresponsive, true. But its still running the main things, the render or decompressing or whatever. So it eventually unfreezes when it completes, by giving other programs(including GUI) back the CPU and ram.

                • boredsquirrel@slrpnk.net
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  6 months ago

                  Ok so killing is worse than just keeping alive.

                  This is a fair point.

                  I dont know a good solution for this, not killing but freezing is likely the best.

                  I dont know

            • Brickardo@feddit.nl
              link
              fedilink
              arrow-up
              1
              arrow-down
              2
              ·
              6 months ago

              Your usual pal won’t be running Blender, they’re going to be stumbling their way through LibreOffice and a browser. Massive echo chamber right there.

      • MonkderDritte@feddit.de
        link
        fedilink
        arrow-up
        5
        ·
        edit-2
        6 months ago

        Why doesnt distros use this by default???

        Nohang has some explanations to this.

        I.e. kernel devs are ignorant to the issue of oomkiller not working as intended on desktop.

        Edit: Lkml is down.

    • marcos@lemmy.world
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      6 months ago

      Just decrease your swap space.

      Unless you have an unusual system, there’s no reason to have several GB of swap.

      • MonkderDritte@feddit.de
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        6 months ago

        Wasn’t oomd the facebook thing for complicated server setups?

        edit: yeah, for large data centers. Imho overengineered for single user desktop sessions. Earlyoom is simple and tiny.

  • CarlosCheddar@lemmy.world
    link
    fedilink
    arrow-up
    9
    ·
    6 months ago

    How come sysreq + f is not on by default? After discovering and enabling it I haven’t had to hard restart due to hangs or crashes.

    • stepan@lemmy.cafeOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      6 months ago

      That restarts the system. This only attempts to kill the app that uses most memory.