I used to use task manager but now I'm using process explorer.
Both have the same problem.
When my pc is crunching away for no known reason, I hit control alt delete >and bring up the task manager via process explorer but things move around
so much I'm always using an eyeball sort - which is inefficient & error >prone.
Obviously I sort by eyeball in the cpu or i/o columns to look for the >offender but the lines move around too quickly - the program need a lag of >about 10 seconds to be temporarily turned on when you're using your
eyeballs to find the offenders (which come and go, I know).
Obviously I can stabilize the sort by pid or process name but then I have
to (again) sort by eyeball to find the constantly changing offenders.
What I want is a program that spits out ONLY something like the top three >offenders when I press a button.
Just that. A static list of the worst cpu (or i/o) users at that moment.
Does such a tool exist?
Have you tried clicking on the CPU header to sort on it? Will that do
what you want?
Also see replies to where you also MULTI-posted, like alt.comp.freeware.
I'll let you know how they worked after I run a few tests since it's important to nail down which process is slowing down the machine the most.
Obviously I sort by eyeball in the cpu or i/o columns to look for the offender but the lines move around too quickly
Obviously I sort by eyeball in the cpu or i/o columns to look for the
offender but the lines move around too quickly
You realise you can speed up or slow down the refresh rate, and even
pause it?
Maybe in Win11 they've even fixed the bug where once you change the
speed you can never get back to the original refresh rate through the GUI?
Andy Burns wrote:
You realise you can speed up or slow down the refresh rate, and even
pause it?
I did not know that. Thank you. But are you talking about Process Explorer? Or the Task Manager
(which Process Explorer replaces)?
On 06-02-2023 16:57 Ken Blake <Ken@invalid.news.com> wrote:
Have you tried clicking on the CPU header to sort on it? Will that do
what you want?
The problem has nothing do to with the sort and I said that in the op.
On 06-02-2023 16:57 Ken Blake <Ken@invalid.news.com> wrote:
Have you tried clicking on the CPU header to sort on it? Will that do
what you want?
The problem has nothing do to with the sort and I said that in the op.
I use System Explorer as a replacement for TM and had the same trouble with CPU. Found a setting that changes Update Speed from Normal to Slow - might there be such in your app?
On 08-02-2023 19:10 PeterC <giraffenos.pam@homecall.co.uk> wrote:
I use System Explorer as a replacement for TM and had the same trouble
with
CPU. Found a setting that changes Update Speed from Normal to Slow -
might
there be such in your app?
Thanks for all the good advice for pausing the output from the various process explorers. I think the best program in some ways is the Memory Hogs program (which works a bit funny so you have to get used to how it works).
It told me within hours that what was hanging up the CPU was Thunderbird. https://i.postimg.cc/sg6DpCc9/hung.jpg
To gather more data, I installed What is Hang from Nirsoft which confirmed. https://i.postimg.cc/Vsg7ShQL/tbhung.jpg
But that brings up a confusing question about the task managers out there.
What's unfortunate is that I couldn't get this obvious and clear "hang" information out of process explorer (which "replaces" the task manager).
In hind sight, does process explorer or task manager have a way to confirm when a process is hung? Is there a way to get it to say "this is hung?"
I mean, it could be using zero resources when it's hung, is that right?
Like, what does a "hung" app do if it's doing nothing?
In other words, looking at process explorer or task manager, how would thunderbird look when it's hung compared to how it looks when not hung?
In other words, looking at process explorer or task manager, how would >thunderbird look when it's hung compared to how it looks when not hung?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 297 |
Nodes: | 16 (2 / 14) |
Uptime: | 03:39:04 |
Calls: | 6,666 |
Files: | 12,213 |
Messages: | 5,335,790 |