I'm not sure whether it is WebKit or the way Apple uses WebKit but something is definitely amiss with Safari for Mac.
I stopped using Safari, moving the Chrome, when it was clear that it continues to use huge amounts of real memory (even with an extension like ClicktoFlash) and at times brings my iMac to a standstill as often as Safari itself gets in a tizzy and decides to force reload all my open tabs. Which is a pity as I much prefer the Safari UI over Chrome's, Safari Reader over Readability, and Safari's inbuilt PDF rendering. Chrome does at least provide a consistent service although I don't like using the address space for both URLs and searches, and printing seems archaic with its own print panel (but it does a better job at rendering web pages for printing than Safari much of the time). Apple just seems to have lost its way with Safari and definitely is a long way from the 'just use it' mindset. Regards, Tony Sent from my iPad On 29 May 2012, at 22:42, Mr P V Hillier-Palmer <[email protected]> wrote: > I find at times Safari freezes means shutting it down and relaunching -- You received this message because you are subscribed to the Google Groups "Sussex Mac User Group" group. To post to this group, send an email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/smug?hl=en-GB.
