App Tamer 2.0.2 Delivers Fixes and UI Tweaks

App Tamer 2.0.2 is available now, providing fixes for a couple of bugs, as well as some minor changes to the UI that help to show what’s going on.

First the fixes:

  • In certain situations, App Tamer 2.0.1 could crash when you launched it. This was due to a bug in the way it tracked subprocesses. The common example was a command in Terminal that ran a couple of other commands which in turn spawned subprocesses themselves. A few simple checks were all that was needed to fix it.
  • A more common problem was that App Tamer would occasionally stop limiting the CPU usage of an application it was supposed to be managing. This turned out to be a timing issue: If App Tamer stopped throttling a process and then immediately started again, the original CPU limiter would still be winding down and App Tamer would find it and use it rather than creating a new one. A few milliseconds later, that CPU limiter would finish shutting down and disappear, leaving the managed application free to use as much CPU as it wanted. App Tamer doesn’t do that anymore 🙂

The UI enhancements:

  • Mark Mackay, an App Tamer user in New Zealand, pointed out that if App Tamer wasn’t limiting the CPU use of an application at the time (because that app wasn’t doing anything) he couldn’t tell if he’d configured App Tamer to slow it down. He suggested I enhance the status indicators that App Tamer puts next to each application to somehow show that running apps – the ones with blue squares – had settings attached to them. A little triangle of color in the bottom right corner now shows you if that app will be slowed down or stopped (with yellow or red corners, respectively).
  • Version 2.0.2 also dims the icon and name of any application or process that can’t be stopped, so you know not to bother clicking on them.

Grab your copy from the App Tamer Release page. The update is free if you’ve bought App Tamer 2!

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Reply