avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • February 24, 2020, 09:37 AM
  • Proudly celebrating 14 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - eFotografo [ switch to compact view ]

Pages: [1]
ProcessTamer / Process Tamer usage tip
« on: May 09, 2006, 08:43 AM »
I've been using Process Tamer for several weeks now (in fact it was what brought me to this site in the first place  :) and it's saved my bacon on a number of occasions already. However a couple of times it was unable to help. Why? Because the ProcessTamerTray.exe process runs at NORMAL priority, and is therefore unable to do its magic when a couple of HIGH priority processes completely take over the CPU!

This exact scenario happened to me recently on a couple of occasions - for reasons I still didn't work out, the latest version of the sysinternals Process Explorer tool began using a full 50% CPU (that is, 100% of one of the two virtual CPUs) on my hyperthreaded P4, without showing the any window. Foolishly I started a second instance instead of Windows Task Manager ... and my machine stopped dead. Two processes, both high priority, eating 100% CPU meant a little over 35 minutes waiting for windows to bring up the task manager to enable me to kill one of the rogue processes.

So where does ProcessTamer fit into this? Since there is (currently!) no option to automatically start ProcessTamer with high priority, the trick is to define an explicit rule to force the priority high. This might seem obvious... but it's not, until your machine is hung and you can't get at ProcessTamer to restore the status quo :)

Thanks Mouser/DonationCoder for a superb tool!!


Pages: [1]