Version 2.4.8 of App Tamer is available. It now explicitly supports the new Music app in Catalina, meaning that if Music is playing something, App Tamer won’t slow or stop it even if it’s in the background.
This release also adds support for Google Chrome ‘Apps’, which you can create in Google Chrome by using the More Tools > Create Shortcut item in the “…” menu in a Chrome window. If you select “Open as window” when creating the shortcut, Chrome creates a separate application that relies on Chrome to render its window. That means that App Tamer needs to (and now will) keep Chrome running, rather than slowing or stopping it, when you’re using one of these separate Chrome apps.
And finally, version 2.4.8 of App Tamer also corrects several issues with its process control mechanism that could result in it not working correctly after your Mac wakes from sleep.
Version 2.4.7 of App Tamer is out. The new release fixes a bug in its “Hide after X minutes” and “Quit after X minutes” features that could cause it to use unreasonable amounts of processor time when they were turned on for iTunes or Spotify. Not exactly what you want to happen in an app that’s designed to reduce the CPU usage on your Mac 🙂
Version 2.4.6 of App Tamer is available, adding preliminary support for macOS 10.16 Catalina (up to the second developer release, anyway, because that’s what we’ve got at present).
It also fixes a little bug that I personally found really annoying: When Spotlight was indexing files, App Tamer showed all of the Spotlight processes separately, often filling up half of the visible process list with Spotlight stuff. It now does what it’s supposed to do, aggregating all the CPU usage in one “Spotlight Indexer” entry and controlling that as if it’s a single process. That gives you better control over Spotlight’s CPU usage and makes CPU-hogs easier to see (I’m looking at you, Spotlight!).
This release also introduces a new setting in App Tamer’s preferences. In the Control tab, there’s now a way to modify how long it waits before managing processes after it launches or wakes from sleep.
This lets you give all processes a little time to run at full speed to get everything synced up after your Mac wakes up, usually making that happen a little faster.
Version 2.4.5 of App Tamer is a fairly tame release – it corrects a few nagging bugs, and is now checked for malware by Apple and notarized to indicate so. The menu bar icon shows its disabled state more clearly when running in Dark Mode on Mojave, and some processes were mistakenly listed in the “Managed Processes” list even though App Tamer wasn’t managing them (ironically, because of bookkeeping error, they were included in the list because App Tamer never touched them at all).
Some users of App Tamer have noticed that version 2.4.3 unexpectedly disappeared from their menu bar. There was a library shared across all of St. Clair Software’s apps that didn’t work correctly in App Tamer, causing it to crash when it received certain system notifications. That’s now been fixed.
Equally important, App Tamer was using more CPU than it had to, which isn’t really what you want in an app that’s supposed to be saving CPU cycles. It primarily affected Google Chrome users, but was actually a problem with all web browsers. App Tamer periodically “rebalances” the CPU usage of browsers’ helper processes, and was actually re-checking to see if the browser was downloading anything every time it did that rebalancing. That was completely unnecessary, and the download check is one of the more CPU-intensive things that App Tamer does, so it really shouldn’t have been doing that more than it absolutely had to.
So, those two issues are fixed – my apologies for the problems. You can grab version 2.4.4 from the App Tamer Release Page.
Version 2.4.3 of App Tamer is available, offering a new option to turn off its AutoStop feature when you’ve been away from your Mac for a specified period of time.
This allows you to stop or slow down background processes so they don’t impact your work, but let them run at full speed when you’re not otherwise using your Mac.
This release also corrects a number of issues, including several crashes that occur in exceptional circumstances and a bug that could prevent apps from returning to full speed when you click on their icons in the Dock. In addition, App Tamer’s ‘wake’ AppleScript command now supports waking up all stopped and slowed apps at once.
Version 2.4.2 of App Tamer is available! There’s an exclamation point there because it offers a fix for an annoying problem that cropped up in Mojave, where Core Graphics Event Taps no longer deliver events to applications when they’re in the background (Radar #45934966 if you’re listening, Apple). While that may sound cryptic, the end result was that App Tamer never saw mouse scrolling events when you used a scroll wheel or gesture to scroll the contents of a background window. If the background window belonged to an app that App Tamer had slowed or stopped, that meant that the window would scroll slowly or not at all. This drove me crazy ALL THE TIME because I apparently scroll through web pages and other background windows very frequently.
Anyway, in addition to that issue, this release improves the ability to move through App Tamer’s process list using the keyboard, and lets you keep App Tamer’s window floating on top of all other windows if want to use it to diagnose a problem or keep an eye on CPU-gobbling processes. A number of little interface issues have also been addressed, and a bug fixed for App Tamer waiting too long to slow or stop background processes when they were also set to be hidden after a certain amount of time.
As usual, this update is free for users who’ve already purchased a license for App Tamer 2.x. You can head over to the App Tamer Release Page to see more details or to download the new version (or just hit “Check for Updates” in App Tamer’s utility menu if you’re already running it).
Jettison 1.7 also includes a number of features and fixes for all versions of macOS (well, from 10.8 to 10.14, anyway — that’s what Jettison supports). These include the addition of a menu command to mount all unmounted disks, options to not automatically remount specific drives after they’ve been ejected, and the fix for a bug that could cause some Macs to repeatedly cycle between sleep and wake. There are also a number of under-the-hood improvements and fixes.
App Tamer 2.4 is now available. It offers a new option to hide applications after they’ve been idle, and also lets you hide its CPU usage graph if you just want to see its lists of CPU-consuming processes. There are also fixes for several bugs, including one that could result in App Tamer not correctly slowing (or un-slowing) an app if you had the “Do not slow or stop apps if power is plugged in” option turned on.
As an additional note, App Tamer works with beta versions of Mojave, but it doesn’t yet support Dark Mode. However, you can switch App Tamer to its own dark appearance and that makes its main window match, at least.
A complete list of changes and a download link are on the App Tamer release page, or if you’re already running App Tamer, you can just choose “Check for Updates” from the menu in the lower right corner of its window.
Version 2.3.5 of App Tamer is available, bringing several improvements and fixes on the performance side, as well as showing you how much CPU time it has saved.
It gives a cumulative “CPU-hours saved,” where a CPU-hour is the amount of computing a single processor core can do in an hour when running at 100%. So if it says it’s saved 8.8 CPU-hours, as shown in the image on the right, that means one CPU would have been running full tilt for an additional 8.8 hours if I hadn’t been using App Tamer. Which means the fans in my MacBook Pro would have driven me crazy today without App Tamer 🙂
Other changes include fixing a memory leak that would cause App Tamer to gradually use more and more RAM if left running for long periods of time, fixing some UI glitches and improving VoiceOver support.
Grab a copy of App Tamer 2.3.5 from the App Tamer Release page, or by selecting “Check for Updates” from its menu if you’re already running it.