• Arthur Besse@lemmy.ml
    link
    fedilink
    English
    arrow-up
    18
    ·
    6 hours 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.)

  • Nailbar
    link
    fedilink
    arrow-up
    11
    ·
    7 hours ago

    I recently had some processes lock up on Linux, and after searching what the “D” symbol in ps aux was (Uninterruptable sleep), i found this little line:

    The only non-sophisticated way to get rid of them is to reboot the system

  • tomjuggler@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    6 hours ago

    Good one! I’m literally dealing with this right now on a server. Turns out you’re expected to deal with long running processes that spawn too many threads yourself, or else…

  • BearOfaTime@lemm.ee
    link
    fedilink
    arrow-up
    6
    ·
    14 hours ago

    Quite often double click on the close button will kill a hung app on Windows. Not Al the time, maybe 70%.

  • flying_sheep@lemmy.ml
    link
    fedilink
    arrow-up
    46
    arrow-down
    2
    ·
    1 day ago

    Tbf, thanks to X11 Linux isn’t safe from stuff like that.

    When I use my VR glasses, Steam sometimes creates an uncloseable X window that isn’t attached to any process. I don’t think even killing XWayland gets rid of it.

  • TunaCowboy@lemmy.world
    link
    fedilink
    arrow-up
    7
    ·
    22 hours ago

    $ kill -l

     1) SIGHUP	 2) SIGINT	 3) SIGQUIT	 4) SIGILL	 5) SIGTRAP
     6) SIGABRT	 7) SIGBUS	 8) SIGFPE	 9) SIGKILL	10) SIGUSR1
    11) SIGSEGV	12) SIGUSR2	13) SIGPIPE	14) SIGALRM	15) SIGTERM
    16) SIGSTKFLT	17) SIGCHLD	18) SIGCONT	19) SIGSTOP	20) SIGTSTP
    21) SIGTTIN	22) SIGTTOU	23) SIGURG	24) SIGXCPU	25) SIGXFSZ
    26) SIGVTALRM	27) SIGPROF	28) SIGWINCH	29) SIGIO	30) SIGPWR
    31) SIGSYS	34) SIGRTMIN	35) SIGRTMIN+1	36) SIGRTMIN+2	37) SIGRTMIN+3
    38) SIGRTMIN+4	39) SIGRTMIN+5	40) SIGRTMIN+6	41) SIGRTMIN+7	42) SIGRTMIN+8
    43) SIGRTMIN+9	44) SIGRTMIN+10	45) SIGRTMIN+11	46) SIGRTMIN+12	47) SIGRTMIN+13
    48) SIGRTMIN+14	49) SIGRTMIN+15	50) SIGRTMAX-14	51) SIGRTMAX-13	52) SIGRTMAX-12
    53) SIGRTMAX-11	54) SIGRTMAX-10	55) SIGRTMAX-9	56) SIGRTMAX-8	57) SIGRTMAX-7
    58) SIGRTMAX-6	59) SIGRTMAX-5	60) SIGRTMAX-4	61) SIGRTMAX-3	62) SIGRTMAX-2
    63) SIGRTMAX-1	64) SIGRTMAX
    
    • kn0wmad1c@programming.dev
      link
      fedilink
      English
      arrow-up
      11
      ·
      1 day ago

      There’s an old addage when working with any Microsoft product:

      “Wait longer”

      In other words, your first click was probably doing its thing. You just needed to wait a little longer to see it work.

      • rtxn@lemmy.worldM
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        18 hours ago

        The wonders of running everything synchronously in the UI event loop…