Originally Posted by Tallest Skil
They did that back in the late 5.x.x set. What problems are you still having?
Yes, Safari 5 was fine, it's only Safari 6 that's broken (which to me coincided with the release of Mountain Lion, but Lion users are experiencing the same issues).
2 - Graphical glitches: Ever since the release of Mountain Lion (and Safari 6), people with MacBook Pros with dual GPUs have been experiencing an issue which under certain conditions causes the browser to display heavy graphical corruption until restarted. This, however, only happens while using the Intel HD300/4000 GPU; switching to the dedicated GPU and refreshing all pages with glitches stops them from occurring. Other Webkit-based browsers, such as Chrome, also display the same issue, and upgrading Webkit does not solve the problem. Just like the memory leaks above, these issues are not initially apparent, they require certain conditions to trigger, but once triggered they will grow progressively worse until the browser is restarted. After months experiencing this, I have finally found a reliable way to reproduce the issue using the Apple Store website and a bit of window resizing (though window resizing is not required to trigger this through normal use).
3 - Privacy mode lacking privacy: For some reason beyond my understanding, Safari is keeping HTML5's local storage around between different sessions of private browsing, after full resets, and even until its directories are wiped from the users' home directories. This only happens to private browsing; resetting Safari works correctly for regular browsing. The only known way to wipe Safari's private browsing local storage data seems to be a complete system reboot. This may or may not be related to the aforementioned issues; my suspicion is that a shared library is allocating shared memory for local storage that is never being freed, and since unlike on other UNIXes, all shared libraries are loaded for all processes being executed in OS X, it is likely that any shared allocations done by those libraries are kept alive on the shared memory allocated for all user processes. If I'm right, not only is tis a privacy problem for the browser itself, but it may also be a privacy problem for individual users of the same system.