• Arthur Besse@lemmy.ml
    link
    fedilink
    English
    arrow-up
    31
    ·
    21 days ago

    I’m not sure what this comic is trying to say but in my recent experience a single misbehaving website can still consume all available swap at which point Linux will sometimes completely lock up for many minutes before the out-of-memory killer decides what to kill - and then sometimes it still kills the desktop environment instead of the browser.

    (I do know how to use oom_adj; I’m talking about the default configuration on popular desktop distros.)

    • QuazarOmegaA
      link
      fedilink
      arrow-up
      2
      ·
      21 days ago

      Real, happened too many times to me. What’s that about configuring the OOM, can you give it priorities?

    • kolorafa@lemmy.world
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      edit-2
      19 days ago

      Linux is slow at killing apps when you run out of memory because it was designed to also run on low spec hardware even if very slowly (making the ui totally unrensposnive) due to swapping.

      This comic is about the kill command, how Linux kernel is handling force stopping apps vs (old?) Windows when if App frozed it was hard to close it. Now with modern apps and hardware you very rarely see that as most apps are designed to have asynchronous logic that is correctly handled, but it’s still more or less relevant.