"After a recent Windows update, some users (including Windows Latest) noticed that closing the Task Manager window was actually failing to close the app, leaving the executable running in memory. More worryingly, each time you open the Task Manager, it spawns a new process on top of the old one, which you can repeat essentially infinitely (or until your PC buckles under the pressure)."
"One reason to use the Task Manager in Windows is to see if any of the apps running on your computer are misbehaving or using a disproportionate amount of resources. But what do you do when the misbehaving app is the Task Manager itself? Each instance of Task Manager takes up around 20MB of system RAM and hovers between 0 and 2 percent CPU usage-if you have just a handful of instances open, it's unlikely that you'd notice much of a performance impact."
After a recent Windows update, the Task Manager can fail to close and leaves its executable running in memory. Each time the Task Manager is opened it can spawn a new process on top of the old one, enabling many instances to accumulate. Each Task Manager instance consumes about 20MB of RAM and intermittently uses 0–2% CPU. A handful of instances produce minimal impact, but dozens of instances can add up and cause noticeable performance degradation and increased battery drain, especially for users who open Task Manager frequently or go long periods between reboots.
Read at Ars Technica
Unable to calculate read time
Collection
[
|
...
]