Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Yes yes, I REALLY want to terminate that process and I am very sure about it too, ty.
you forgot that you have to spend about 2 minutes with windows "searching for a solution" (who knows what that does??) and then another minute reporting it to microsoft
My problem with Windows is that when I want to eject a USB drive, Windows refuses to do so, refuses to tell me what program is apparently still using the drive, and certainly refuses to kill that program. I am removing the drive. I can't just not remove it!
The worst part is that with Quick Removal it's pretty much always safe to just remove it
I've found that in those cases its usually explorer that's the culprit. Just having the removable drive open in explorer is enough to keep windows from being able to unmount the drive.
KDE now too
KDE can murder windows instantly (you have to set a shortcut), or you can also just send SIGKILL to the process
xkill is one of my favorite commands
Is there a Wayland equivalent?
Open the process list in your system monitor of choice, right click, signal, sigkill.
You can also open a monitor and use top or any variant to detect the process number and manually kill -KILL number
I really want the convenience of binding xkill to a key, which I can use to double tap programs like the undead zombie they've become.
Dunno, create a script that uses a program to get the process number of the current active window or the window the mouse is hovering, and then kill that? Bind that script inor a key with whatever program and voilá.
It's more involved sure but there's your option.
Great idea, now I just need to know how to do that.
Get learning lol. I know that there's some command line program that gives process info on mouse hover and then that can be parsed with awk to get the pid, then pipe that again into kill -kill. Then use xbindkeys or whatever keybindings program to bind that script to a key.
Tbh. For involved stuff like this chatgpt will help you more than stackoverflow.
I dunno; I sadly can't use Wayland yet bc I have Nvidia
I don't know if you heard, but the Nvidia issues are solved (mostly).
The issue most people had was with Explicit Sync, which was patched in the proprietary Nvidia driver 555 which is upstream on most distros.
Good to know; I'll check it out!
Typing “kill -9” into a terminal is the equivalent to breaking out the acetylene torch when a nut won’t budge
Can't be tight if it's liquid
It even kills threads currently executing a system call! The brutality!
Never even returned to userspace…
ps aux | grep . kill
kill -9 $(pidof )
killall works great for this.
At that point you can just hard restart as well. Most motherboards accept 10 to 15 seconds of power button as "my OS is fucked please help" and restart the machine for you.
killall just kills all instances of a program, not everything.
and also, long pressing the power button should just shut it down, no?
They also accept pulling the power cord out as "oh no" and shutdown for you!
How the OOM Killer asks a process to terminate:
indiscriminate spraying
mainly wrong, by default kill send a SIGTERM, you can try SIGINT or SIGQUIT too, and in the end SIGKILL of course. Same in windows there is different way
I always go straight for the SIGKILL
Every time you SIGKILL, a poorly-drawn penguin dies!
Some software: fork()
Me: Welcome to the process gauntlet loser, better not hang for a millisecond or you are dead and gone.
And as always with this meme: Both Windows and Linux can ask a process nicely to terminate or kill it outright. And the default for both is to ask nicely.
on windows a process can get in a state so that it is impossible to make it go away, even with process explorer or process hacker. mostly this also involves the bugged software becoming unusable.
I encounter such a situation from time to time. one way it could happen is if the USB controller has got in an invalid state, which one of my pendrives can semi-reliably reproduce. when that happens, any process attempting to deal with that device or its FS, even the built-in program to remove the drive letter, will stop working and hang as an unkillable process.
Linux has that issue too. A process in an uninterruptible blocking syscall stays until that syscall finishes, which can be never if something weird's going on.
I've seen that on Linux as well. Funnily enough also with faulty file systems. I think NFS with spotty wifi for one.
Oh, and once with a dying RAID controller. That was a pain in the ass. At that point I swore to only ever do RAID in software.
Windows can kill a process outright.
Hmmmm...
Taskkill /f is reasonably close to sudo kill -9
Hitting the X in Windows and hitting the X in Linux both cause the application to start a save yourself routine. From the OS standpoint they're not far off.
The problem is we have a lot of confirmation bias in windows because every time we want to close an application that's not working, that save yourself call has to sit around for a hellaciously long time out followed by a telemetry call so that Microsoft can track that it happened.
It's pretty rare that Linux apps don't just close.
Because that's better for the software, Linux however kills it outright when it doesn't respond at all. Windows just... Waits. And you can't really hardkill the processes from the task manager. Or at last my last knowledge is that.
You can easily make a program unkillable (or to be more precise untermable) on Linux. Here's a simple bash script that will do that.
#!/bin/bash function finish {
while true
do
echo "Can't kill me."
sleep 10
done
} trap finish EXIT
trap finish TERM
trap finish INT
while true
do
echo "Still alive."
sleep 10
done
League of Legends captures and discards the ALT-F4 keystroke combination.
Microsoft trusts app developers to use Microsoft's standards (such as terminating the process when a close message is received) and they shouldn't. App developers like Riot have taken advantage of this trust and tuned their apps to act differently than expected, and include code which makes the app minimize to the system tray instead, or force the user to answer questions ("Are you SURE you want to close?"), or do nothing at all.
It should be punishable by death.
Linux programs can also capture signal calls. They usually only capture sigints so that they can close gracefully, but theoretically you could also capture a sigkill.
I mean, "are you sure" is useful... sometimes
Well, with linux you get the option of sending mixed signals through the use of varying count of guns. I find 9 to be highly effective.
Next, you'll tell me I shouldn't get all my news from memes!
I feel like I've had the opposite experience in the gui (maybe a KDE issue?) closing gui windows frequently lock up, and I find I frequently have to drop to the command line in order to properly kill some programs
That's because the end proces of the GUI sends a sigint, which does jack shit if the program hangs, you only archieve for a higher parent process to obtain it until it can off itself gracefully. You need to right click the process and send a sigkill signal to emulate the command line.
Sigterm: "End this process or next time I bring my -9"
My tec-9
TerminateProcess() is pretty reliable, but it doesn't form part of the C signals stack on Windows like kill -9. So for instance, if you're doing process control on Python, you need to use a special Windows-only API to access TerminateProcess().