Downloaded and installed the Mac OS X 10.3.9 update (ala a service pack in the windows world) but ran into some problems straight after the reboot. Safari started crashing everytime I closed a window or a tab. Tried the repair permissions and reboot routine, to no avail. Visited the Macrumors forum to see if anyone else was experiencing the same. And sure thing, a lot of people who had one Safari plugin or the other were experiencing crashes.
This post, for example, mentions the cause as well as the solution of one such crash. This, incidentally, was exactly what was happening on my system as well, as I have iGetter installed and integrated with Safari. Moving the said folder to a “safe” location has solved my crash issues – so far. People with other Safari plugins have reported similar problems and (the same) method of resolution. So if you’re using experiencing similar issues I would suggest moving the folders in question to see if that helps. If not, drop in here and you might find someone who’s facing the same problem and/ or will be able to help you out.
Safari has gone up from 1.2.4 (v125.12) on my machine to 1.3 (v312). Obviously, the developers have changed some code which has an impact on the way these plugins interact with Safari, so until the third party applications come out with updated versions of their plugins, we’ll have to live without them.
This is the first time I have experienced any kind of issues after an update. Though, to be fair to Apple, they have clearly mentioned that such issues may occur after the update:
You may experience unexpected results if you have installed third-party system software modifications, or if you have modified the operating system through other means. (This does not apply to normal application software installation.)
I guess Safari qualifies as “system software” then?
I can’t remember if that’s the “standard warning” for every update or something that has been issued this time round because they anticipated this kind of issues.
On the brighter side, Safari download now displays the speed at which each individual download is being clocked and is supposed to be faster, but I haven’t really had a chance to experience that yet.
“It just works.” 😉