Okay, I guess it's time for me to do some community service. I'm NOT having ANY problems with Safari or the walled silo that Apple built for plugins that *ahem* misbehave, 'Web Content'.
To those of you who are using Click to Flash, good. That's a start, but here are my sugggestions:
1/ If you have it, Shut off Java not only in Safari but also in the Java Preferences.app in /Apps/Utilities/JavaPreferences.app "Enable Applet & Web Start Plugin" to UNchecked. It should be already shut off if you didn't touch it & you applied the most recent Java security update.
2/ Instead of running Click to Flash, consider installing the 'Click to Plugin' which also allows you to halt the loading of more than just the Flash plugin. See here:
http://hoyois.github.com/safariextensions/clicktoplugin/
This will stop plugins, even 'hidden web bug' like ones that the authors of the web pages don't want to you see from automatically loading. I just do not buy that 'Web Content' just 'runs up' for no reason. There's something banging around in that silo. It'd be nice to find out what it is.
"Click to" will show placeholders instead of the plugins, then you can find out (at least it's easier) what thte culprit is. Flash, Silverlight, Shockwave, Java, Quicktime will all get placeholders if they 'render' on a web page. Even HTML5 Objects.
3/ Finally, and I'm going to make you power users Google this... You can turn on Safari's 'Debug' menu and run memory samples. And then use Apple's Feedback web form to tell them how and why Safari 6 is sucking for you.
Personally I've expunged Flash (since Lion, actually) as well as Perian from my MoLion MacBook Pro. And more recently, Flip4Mac. And I'm NOT having these problems. But if it *is* the hardware, then Apple needs to know via feedback.
-Leo