• Dr. Wesker@lemmy.sdf.orgEnglish
      29·
      4 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.pubEnglish
        21·
        4 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.

          • henfredemars@infosec.pubEnglish
            1·
            3 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
        2·
        3 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
        1·
        3 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.

  • archonet@lemy.lolEnglish
    17·
    3 days ago

    SIGTERM: stop that.

    SIGKILL: That was not a request.

    Case power button: listen here you little shit

    • letsgo@lemm.ee
      2·
      3 days ago

      Sounds like it’s not just me that goes “ok then, try arguing with this” when power cycling an unresponsive computer.

    • gamermanh@lemmy.dbzer0.comEnglish
      5·
      3 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

    • prole@lemmy.blahaj.zone
      0·
      3 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.zoneEnglish
        4·
        3 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
    3·
    3 days ago

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

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