Yesterday we reported a serious problem with Safari 1.2.1 and FedEx's Web-based package tracking mechanism where certain tracking URLs will result in a Safari-specific freeze, which allows the user to force-quit Safari after a few attempts. Some users, however, find that after using a problematic URL, Mac OS X is no longer responsive and a system restart is required.
In some cases, Safari may not have actually frozen, and will resume operation after several minutes. Melvyn Goldstein writes "I ran across that yesterday, but found that despite claim from Activity Monitor that Safari was hung, it really wasn't. If I waited several minutes (go get a cup of coffee), the page would finish loading (it seemed to be the last item to load that 'hung' Safari) and all would be well, again. I repeated that experience at least 3 times while trying to figure out who signed for a package."
OmniWeb 5.0 (Beta 5) is also affected by this problem as it is based on the same webcore as Safari.
Some users have received a response from FedEx's technical support department indicating that they are working on the problem, and recommending interim use of Netscape or Internet Explorer.