• Dr. Wesker@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      40
      arrow-down
      1
      ·
      edit-2
      18 days ago

      All the damn time. I typically use Linux, so having a process I can’t even force kill is a severely annoying concept.

      • henfredemars@infosec.pub
        link
        fedilink
        English
        arrow-up
        32
        ·
        edit-2
        18 days ago

        This has happened to me only once on Linux. I still tell stories about it.

        It was a CD burning program stuck in uninterruptible sleep! Trapped in a system call into the kernel that can never be interrupted by a signal, it was truly unkillable. The SIGKILLs simply piled up never to be delivered.

        • Lost_My_Mind@lemmy.world
          link
          fedilink
          arrow-up
          19
          ·
          18 days ago

          THIS is your big “You won’t believe what happened to me…” story???

          sigh

          When I was 14, I took the power cord for the original PS1 and shaved the rubber off the end until metal prongs were sticking out. Then I noticed if the outlet end was plugged in, and you touched the metal prongs on the other end, you couldn’t drop it. It would electricute you, but it would also stick to your skin for 5-10 seconds as it electricuted you.

          So being a 14 year old male, I did the only logical thing. I put it on my penis.

          It was quite shocking!

          • henfredemars@infosec.pub
            link
            fedilink
            English
            arrow-up
            3
            ·
            edit-2
            18 days ago

            In this case it was a driver holding that thread captive and making an assumption about the hardware eventually responding to a request which never completes.

            So yes indeed it was the kernel, and ideally the driver could be written better, but that’s probably easier said than done when the hardware can do weird things.

            This was a long time ago, so for all I know the issue has been long corrected.

      • laranis@lemmy.zip
        link
        fedilink
        arrow-up
        2
        ·
        17 days ago

        It honestly was the thing that pushed me to Linux. Once I could no longer kill programs at-will I couldn’t handle it. xkill ftw.

      • nickwitha_k (he/him)@lemmy.sdf.org
        link
        fedilink
        arrow-up
        1
        ·
        18 days ago

        Yeah… It doesn’t happen often and when it does, it’s usually a driver and/or hw issue that is likely to leak memory and/or hold file descriptors but procs in D (uninterruptible_sleep) state do happen. It’s really obnoxious that murdering them with SIGKILL does nothing.

    • Magikjak@lemmy.world
      link
      fedilink
      arrow-up
      9
      ·
      18 days ago

      A while ago I kept a shortcut in the taskbar that ran a batch file that killed any unresponsive task, worked even on those tasks that Task Manager can’t seem to close. As long as explorer was still running and I could alt tab and press that button it worked 100% of the time

          • flambonkscious@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            4
            ·
            18 days ago

            That’s proper mental, I don’t know why you’d keep that running unnecessarily (unless fiddling with something you can easily replicate).

            Im pretty sure it’s still not going to catch the stuck things that aren’t actually killable

            • Magikjak@lemmy.world
              link
              fedilink
              arrow-up
              4
              ·
              18 days ago

              It wasn’t something I kept running, just a shortcut that would run the batch file and kill anything that wasn’t responding at the time. I’m not sure if this uses the same command I had set up at the time, but I remember it having a 100% success rate. I had it for one game in particular which would crash and stop responding but any attempts to get to the task manager (even with keyboard) would fail.

              I haven’t had to use anything like this since Windows 10 as now you can just press Windows+Tab and move the task to a different desktop and then get into the task manager on your original desktop.

  • archonet@lemy.lol
    link
    fedilink
    English
    arrow-up
    27
    ·
    18 days ago

    SIGTERM: stop that.

    SIGKILL: That was not a request.

    Case power button: listen here you little shit

  • RegalPotoo@lemmy.world
    link
    fedilink
    English
    arrow-up
    26
    ·
    18 days ago

    Meanwhile, a Linux user wipes blood off a sledgehammer with “SIGKILL” written on the handle

      • RegalPotoo@lemmy.world
        link
        fedilink
        English
        arrow-up
        11
        ·
        18 days ago

        In the immortal words of Monzy:

        I pull out my keyboard / and I pull out my gloc / and I dismount your girl / and I mount slash proc / cos I’ve got your pid / and the bottom line / is you best not front / or its kill dash nine

      • finley@lemm.ee
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        18 days ago

        Lol, tell that to Xorg.

        130% and it doesn’t care about your kills or killalls or pkills or SIGKILLs…. It’s just gonna go, no matter what, until you shut the fucker down by unplugging it.

        Sometimes you’ve just got a process that just won’t listen to commands.

        Thants when you have to KILL the process.

        • PlexSheep@infosec.pub
          link
          fedilink
          arrow-up
          9
          ·
          18 days ago

          Ig you sigkill a process, that process will no longer get CPU time, as far as I know. So if it didn’t work, you shot the wrong thing.

    • I_Miss_Daniel@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      18 days ago

      Doesn’t seem to work for me. If Rustdesk goes rogue, it refuses to die. I might need to practice some more command-line-fu though.

    • gamermanh@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      7
      ·
      17 days ago

      One time I was playing modded Skyrim when it froze/crashed at the loading screen

      So I summon task manager, it hides behind the frozen game. I alt+tab and start blind keying to Skyrim to end it, been here hundreds of times, but nothing happens and the Skyrim world music STARTS???!!!

      ALT+TAB to see TM and Skyrim both reporting non-responsive. Tab to Skyrim and press w, clearly hear character moving and reacting to my input

      Try again to end process via ALT+F4, No dice. Try via TM, still unresponsive

      I had to reboot my PC with a hard power button press that time and I still don’t fully understand what the FUCK happened

      • ArxCyberwolf@lemmy.ca
        link
        fedilink
        arrow-up
        5
        ·
        17 days ago

        New Vegas does the same thing, hiding Task Manager behind itself when it crashes. I found a workaround by using Ctrl+Alt+Del, clicking to make the cursor appear, and then pressing the Windows key which makes the taskbar appear. Then the game window can be closed from the taskbar.

    • prole@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      17 days ago

      As someone who’s relatively new to Linux, anyone want to explain what these lines would do? I’m aware of KILL, but dunno what the ‘-9’ refers to. Not familiar with sysrq-trigger

      • BougieBirdie@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        4
        ·
        17 days ago

        The kill command allows you to specify which type of kill signal you want to send. -9 sends signal 9 or SIGKILL, and we’re sending it to pid 1.

        That would force kill systemd, which I just have to assume will send your computer to a crashing halt.

        The echo command is writing "c" to a file at /proc/sysrq-trigger which I don’t really know how it works but this suggests you’ll “crash the system without first unmounting file systems or syncing disks attached to the system.”

        I haven’t installed fuck so I’m not sure how that works

  • Demdaru@lemmy.world
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    18 days ago

    As a windows user WIN+R -> CMD -> TASKKILL /F /T /IM “<appname>*”

    … I use it too much. Appa often block my screen :|