Apple goes on a bug bashing safari

newsguy 1 304 Views

Safari 4.0.3 is out now and available for download from Apple, for both Mac OS X and Windows operating systems.

While there are the usual claims of making things more stable when using third party plugins and in particular for handling the HTML 5 video tag, it is with regards to security strengthening and bug squishing that the real interest lies.

So with the latest update Apple says it has fixed issues which impacted upon users logging in to the document sharing service, an Apple service embarrassingly enough and I should have said prevented users logging on to be precise. Other bugs trampled underfoot include an odd retro effect one which could make some content online display not in colour but in a grey scale rendering instead.

Apple calls them security fixes, I say they are simply more bug fixes by another name. Whatever the semantics of the situation, Apple has patched an EXIF data flaw which could lead to a remote code execution on the Windows platform, the same flaw which had already been resolved for Mac users incidentally. What else, about the only thing of note I can see is the beefing up of floating point processing code to prevent buffer overflow exploits.

Dani AI

Generated

Good summary, . A few practical, hands‑on notes follow that expand on installation and common troubleshooting after a Safari update.

  • Confirm the installed build via the About dialog (macOS: Safari → About Safari; Windows: Help → About).
  • Perform a full restart of the browser and the OS after installation so shared libraries and plug‑ins reload.
  • Reset site data and caches using Safari’s Reset/Clear options; back up bookmarks and saved passwords first because reset operations remove them.
  • Isolate extensions and plug‑ins: disable all extensions in Preferences → Extensions, then move third‑party plug‑ins out of /Library/Internet Plug‑Ins and ~/Library/Internet Plug‑Ins to a temporary folder and reintroduce them one at a time.
  • To distinguish a site/server problem from a client issue, test the site from a private window or an alternate browser and clear site cookies for the affected domain.

Collect diagnostic evidence before making sweeping changes. On macOS, Console.app and CrashReporter entries (look for Safari/WebKit labels) give the backtrace; on Windows, check the Application logs in Event Viewer. A fresh user account or clean browser profile is an effective way to tell whether a problem is account‑specific. When deleting preference or cache files, create a copy first — plist removal or cache deletion will remove saved settings and session state.

Display or media anomalies often trace to third‑party codecs or outdated graphics drivers rather than the browser core. For stability and security, keep the OS, browser and media plug‑ins up to date, and collect exact build and platform details when escalating diagnostics. Security hardening frequently resolves functional bugs as well, so treating updates as both stability and safety improvements is appropriate.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.

Edit Preview