Comments on: Automatically Kill Hung Applications

By: Alter Falter!

Alter Falter! — Mon, 27 Aug 2007 19:53:22 +0000

Hmm, too bad: My AutoEndTasks is already set to 1…?

By: Kip

Kip — Sun, 26 Aug 2007 07:01:32 +0000

I’ve across this “tip” a dozen times. Don’t rehash old stuff.

By: Automatically end hung applications » The PC Doctor’s blog

Automatically end hung applications » The PC Doctor’s blog — Sat, 25 Aug 2007 09:17:23 +0000

[...] Excellent Windows XP tip on gHacks : [...]

By: Joe

Joe — Sat, 25 Aug 2007 08:54:37 +0000

Martin, I’m not sure I understand this.
Are the two keys connected and dependent on one another? In other words, do I need to set autoendtask to 1 in order to set the delay or should it be set to 0 and only then I will get the delay that I set in the other key?

Also, what does it mean “the process is terminated instantly”? How does the system know when a process is hung?

Thanks’
Joe

By: Roman ShaRP

Roman ShaRP — Sat, 25 Aug 2007 08:34:55 +0000

Do you about Process Lasso or Process Tamer?

Those are applications for “automatic priority management”. Both are about lowing priority of processes, consuming too many CPU time {and in such way allow to kill troubled app without much waiting}.

Process Lasso in addition
- can automatically raise priority for chosen process and make it work faster or not interruptable by other
- can boost foreground process priority
- has nice CPU usage or system responsiveness indicator
- can show memory usage and so on

So, when I start using Process Lasso, I throw out famous Process Explorer – not only because of problems I had with it, but because Process Lasso can replace it and do more for me {but looks not so good, heh :) }.

And both are free. I do not tets Process Tamer, because Lasso work fine.