3 ms·
I have been where you are, posting the same thing, but I don't believe it is true today. Applications that hang and can't be killed is a much bigger problem to
by Dah00n 4y ago
I have been where you are, posting the same thing, but I don't believe it is true today. Applications that hang and can't be killed is a much bigger problem to me in Linux than in Windows 10. I also don't reformat, at most i reset Windows or applications but it has been years. I agree with the rest but in everyday use the registry is not a problem in Windows.
The difference to me is that I as a power user might be able to fix it myself in Linux but by only using the tools normal users know of I must say I cannot recognize that this is a weak point in Windows today. Clicking the X to close an app and getting stuck with a dead app is much worse in, say, Debian than in Windows.
With that said.. I don't use Windows where I have a choice but that is mainly for philosophical reasons these days. Mac I don't touch. I feel it is the worst of both camps.
- AnimalMuppet 4y ago> Applications that hang and can't be killed is a much bigger problem to me in Linux than in Windows 10. Have you seen anything in Linux that you can't kill with "kill -9"?
- wazoox 4y agoI have a nice shortcut : Windows+K calls "xkill" :)
- aaronmdjones 4y agoOn Linux, processes that are stuck in D state (waiting on I/O) cannot be signaled. More specifically, the signal will be queued until the task exits that state. This includes signal 9. The process may well never exit that state, for example if the I/O it's waiting for is actually over a networked filesystem and the NIC is misbehaving.
- kccqzy 4y agoFortunately we have TASK_KILLABLE to replace TASK_UNINTERRUPTIBLE. https://lwn.net/Articles/288056/ https://lwn.net/Articles/288056/