I've been using Hardware Growler for nearly as long as it has been around without issue, but I recently ran into troubles with my new Time Capsule, and someone on Apple's forums pointed the finger at Hardware Growler.
While the Apple Discussion (linked below) sums up the issue in full, I'll reiterate here:
My new Time Capsule houses my iTunes library. The music is essentially streamed to my MacBook. About once every 2 or 3 minutes, Hardware Growler notifies me that I've connected to my airport network (without ever telling me I disconnected) at which time my music will stop and take 10 seconds to rebuffer. If Time Machine was running a backup, it would hang and take several minutes to timeout. I was told this was a bug in the Airport Extreme / Time Capsule software, and a quick fix is to run iStumbler all the time. This creates a Growl issue in itself, because running iStumbler in a city environment produces a TON of annoying notifications (only some of which are actually useful to me). Today, someone posted the following reply:
HardwareGrowler causes the Airport disconnects, AFAICT. It shows the same problem as MarcoPolo and other software that poll the Airport interface. Try to disable hardware growler and I'm ready to bet your connection will be much more stable. MarcoPolo's developer explained to me this was due to having to use some clunky way of querying the network interface, as OSX didn't offer a clean way to do it. I still have this problem with X.5.4.
My response to him is the same I offer the Growl community -- I love Hardware Growler and don't want to get rid of it, so I'd love if someone paid attention to this complication.
Apple Discussion Link
Thanks in advance for any replies!