


(Because nothing in the user interface runs with real-time priority.) It won’t help because you first need to be able to launch Task Manager (or switch to it, if you were prescient enough to have it already running), and none of the ways of launching Task Manager run with real-time priority. One might argue that Task Manager should run with real-time priority, so it can extricate you from this situation, but that won’t help, and it would be wrong. Sure, it could receive your input and distribute it to the appropriate application queues, but those applications are themselves not running with real-time priority, so all that happens is that your input gets quickly transferred to the input queues, where it then sits waiting for the applications to process them (which will never happen since the applications are not running with high enough priority). Mind you, even if the input thread did run at real-time priority, that wouldn’t really help you any. In particular, since not even input runs at real-time priority, you can’t stop it via any interactive means, because the thread that manages input can’t even run to process your input. If you foolishly set the priority class of a CPU-intensive program to real-time, it will suck up your entire processor, leaving no cycles for anything else. It’s higher priority than mouse input, keyboard input, and the disk cache. It’s higher priority than nearly everything else.
