But I also remember the times when there was no foe Task Manager could not kill.
Comment on Choosing violence
henfredemars@infosec.pub 2 years ago
I have encountered processes that even Task Manager could not kill.
SpicyLizards@reddthat.com 2 years ago
Magikjak@lemmy.world 2 years 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
henfredemars@infosec.pub 2 years ago
How do you determine if a task is unresponsive?
Magikjak@lemmy.world 2 years ago
It was something like this. It would just kill all tasks that haven’t responded in X amount of time. Obviously this is not a great solution as it can cause data loss and you could accidentally close more than just the program you intend to close, but sometimes you have little choice.
flambonkscious@sh.itjust.works 2 years 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
aeronmelon@lemmy.world 2 years ago
“This computer is hereby deconstituted.”
wesker@lemmy.sdf.org 2 years ago
All the damn time. I typically use Linux, so having a process I can’t even force kill is severely annoying.
henfredemars@infosec.pub 2 years 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.
Lost_My_Mind@lemmy.world 2 years 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 2 years ago
I used to stick forks in the electrical outlets.
Now I post Linux memes.
Honytawk@lemmy.zip 2 years ago
I can’t believe what happened next
lolrightythen@lemmy.world 2 years ago
Image
Lost_My_Mind@lemmy.world 2 years ago
I…can’t tell what is happening here. Is he having an orgasm? Is he supposed to be a priest, or a slave?
Ziglin@lemmy.world 2 years ago
I would assume that was a kernel issue.
henfredemars@infosec.pub 2 years 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 the reality is that’s probably easier said than done when the hardware can do weird things.
laranis@lemmy.zip 2 years 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@lemmy.sdf.org 2 years 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 withSIGKILLdoes nothing.