Bugs & Fixes: Safari 3.2 plus Input Managers equals crashes Miami FL

As noted in this Apple document on the Cocoa Application Framework: "The automatic loading of bundles located in InputManagers folders is now officially unsupported. The conditions for valid input manager bundle is further tightened. This functionality is likely to be disabled in a future release."

In other words, Input Managers are on the way out. And, while they may still work for now, don't count on things to go smoothly. In particular, when Apple updates Safari, it pays little or no attention to whether the update may break the ability of existing Input Managers to work. Often, a Safari update and installed Input Managers conflict, with Safari crashing as a result.

The immediate fix is to remove the problem Input Manager from your Library/InputManagers folder. With luck, the developer of the Input Manager software will release an update that is compatible with the latest Safari version. One such update already exists for PithHelmet and Safari 3.2. The best long-term solution is to give up on Input Managers altogether, instead of waiting for them to become extinct in the next version of Mac OS X.