How can windows task manager close frozen program which we cant by clicking on close button?
In: 27
Think of your computer as a bus. All of the people on the bus are programs.
The bus driver is one of the people on the bus, and the bus driver has both a special job to do (make the bus go) and has special authority over the other people on the bus.
Everybody who isn’t the bus driver (all other programs) has to interact with the bus driver in order to get on the bus, ride the bus, and get off the bus when they’re done riding.
Now think of a program freezing on your computer as a rider misbehaving on the bus. At that point, nothing any of the other riders do is going to make that person stop misbehaving.
The bus driver has special privileges, though, and one of those privileges is to force riders to exit the bus. Sometimes the bus driver acts on their own, detecting that a rider has misbehaved, and forcing that rider off the bus. Other times, though, it’s not as obvious to the bus driver, and so a passenger has to go tell the bus driver that there is a passenger misbehaving.
When you click the close button on an individual program (a bus rider), you are politely asking that rider to stop what they’re doing and exit the bus. When you click the End Task button in Windows Task Manager, you’re asking the bus driver to unceremoniously yeet that rider off the bus.
(Also in this bus analogy, sometimes things go so wrong on the bus that the bus driver just drives off a cliff and kills everybody.)
When you click the close button, it starts a shutdown process where the program might clean up memory, save state, and other background tasks. If the program is frozen those can’t run, so it doesn’t close.
When you force close, the operating system is killing the process without regard for any shutdown processes.
That’s not 100% always accurate but you can think of it like that in an ELI5 sense.
Think of your computer as a bus. All of the people on the bus are programs.
The bus driver is one of the people on the bus, and the bus driver has both a special job to do (make the bus go) and has special authority over the other people on the bus.
Everybody who isn’t the bus driver (all other programs) has to interact with the bus driver in order to get on the bus, ride the bus, and get off the bus when they’re done riding.
Now think of a program freezing on your computer as a rider misbehaving on the bus. At that point, nothing any of the other riders do is going to make that person stop misbehaving.
The bus driver has special privileges, though, and one of those privileges is to force riders to exit the bus. Sometimes the bus driver acts on their own, detecting that a rider has misbehaved, and forcing that rider off the bus. Other times, though, it’s not as obvious to the bus driver, and so a passenger has to go tell the bus driver that there is a passenger misbehaving.
When you click the close button on an individual program (a bus rider), you are politely asking that rider to stop what they’re doing and exit the bus. When you click the End Task button in Windows Task Manager, you’re asking the bus driver to unceremoniously yeet that rider off the bus.
(Also in this bus analogy, sometimes things go so wrong on the bus that the bus driver just drives off a cliff and kills everybody.)
Basically you have the app layer and the system layer. When you press buttons and click things in the app you’re interacting with the app that then has to pass requests on to the system. If it’s locked up, it can’t pass those requests on at all.
The task manager is dealing directly withthe system layer and it gives you power that you don’t normally have. If an app were a house of cards on a table, task manager is like the legs of the table. Knock one out, and the house of cards will definitely fall.
Simplistic ELI5 is:
Imagine you have a new white board — This is your app/program that you just started eg MS word.
You are drawing in it — You are writing a word document.
Close –> erase the white board and remove it from the wall.
Task manager close –> Just remove it from the wall because your brother plastered the drawing pane with tape and you cant erase it anymore.
In OS, the thread(white board) which holds the program ie MS Word (drawing) is just killed (removed from the wall) rather than closing (erasing the drawing) and then closing the program.
Simplistic ELI5 is:
Imagine you have a new white board — This is your app/program that you just started eg MS word.
You are drawing in it — You are writing a word document.
Close –> erase the white board and remove it from the wall.
Task manager close –> Just remove it from the wall because your brother plastered the drawing pane with tape and you cant erase it anymore.
In OS, the thread(white board) which holds the program ie MS Word (drawing) is just killed (removed from the wall) rather than closing (erasing the drawing) and then closing the program.
Basically, when you run a program, it is its own program. Everything in & on that window is part of it; including the close button. Pressing the button is asking the program to end itself, which won’t work if the program is frozen for one reason or another
Task manager doesn’t interact with the program. It tells the computer “hey, you’re having an aneurysm here, I’m nuking it off your memory”
Basically, when you run a program, it is its own program. Everything in & on that window is part of it; including the close button. Pressing the button is asking the program to end itself, which won’t work if the program is frozen for one reason or another
Task manager doesn’t interact with the program. It tells the computer “hey, you’re having an aneurysm here, I’m nuking it off your memory”
Latest Answers