When you click the “close” button you are politely telling the program to exit. It is informed to gather its things, and leave the premises in a timely fashion.
When you click the “end task” button you are forcibly booting the program from the computers processing space. The OS will immediately dispose of the running program and free up the space for other things.
If you were to compare it to leaving a hotel, the former is having a bellhop show up at your door with a luggage cart to escort you to checkout, and the latter is a security guard dragging you out by the ear and tossing your belongings in the dumpster.
When you click the “close” button you are politely telling the program to exit. It is informed to gather its things, and leave the premises in a timely fashion.
When you click the “end task” button you are forcibly booting the program from the computers processing space. The OS will immediately dispose of the running program and free up the space for other things.
If you were to compare it to leaving a hotel, the former is having a bellhop show up at your door with a luggage cart to escort you to checkout, and the latter is a security guard dragging you out by the ear and tossing your belongings in the dumpster.
The close button lets the program close in the way it should, using Task Manager kills the process(es) so it stops running.
For ELI5.
A bar customer is asked to leave nicely and does so – normal close.
A bar customer is behaving badly and needs a bouncer (Task Manager) to get them out – ends the running process, it’s had enough of their behaviour.
Because it “kills” the process by straight up stopping it no matter what operations it is performing. Clicking the close button meanwhile just tells a program to start a “close” operation, which of course will go nowhere if the program is frozen as it cannot process any more operations until it unfreezes.
Task manager just abruptly kills the program’s main process which cascades to kill all subprocesses (ideally) and cleans up the memory (ideally). Nothing talks to the program so it doesn’t matter what’s it doing. It’s sort of like plugging the electricity plug to your computer: it will just shutdown no matter what
The close button lets the program close in the way it should, using Task Manager kills the process(es) so it stops running.
For ELI5.
A bar customer is asked to leave nicely and does so – normal close.
A bar customer is behaving badly and needs a bouncer (Task Manager) to get them out – ends the running process, it’s had enough of their behaviour.
Hitting the close button is like asking someone to leave the restaurant because it’s closing time. Most will go without a fuss, but some throw a fit and insist that they be allowed to interrogate the manager. They’ll eventually clean up most of their mess and go… but they’ll take their sweet time.
Killing a process through the task manager is having the manager whip out a shotgun, shoot the customer, and toss their body in the dumpster out back. It gets the job done immediately, but it tends to leave a little bit of mess since the program couldn’t stop gracefully.
Task manager just abruptly kills the program’s main process which cascades to kill all subprocesses (ideally) and cleans up the memory (ideally). Nothing talks to the program so it doesn’t matter what’s it doing. It’s sort of like plugging the electricity plug to your computer: it will just shutdown no matter what
Hitting the close button is like asking someone to leave the restaurant because it’s closing time. Most will go without a fuss, but some throw a fit and insist that they be allowed to interrogate the manager. They’ll eventually clean up most of their mess and go… but they’ll take their sweet time.
Killing a process through the task manager is having the manager whip out a shotgun, shoot the customer, and toss their body in the dumpster out back. It gets the job done immediately, but it tends to leave a little bit of mess since the program couldn’t stop gracefully.
Latest Answers