You should start eliminating these:
+net.culater.SIMBL.osax (0.9.9 - 0.9.9) <F0F26DED-2BF8-C0BF-8D26-30D50D989095> /Library/ScriptingAdditions/SIMBL.osax/Contents/MacOS/SIMBL
0x10eb77000 - 0x10ebafff7 +com.hetima.SafariStand (6.0.184 - 6.0.184) <A69A44A1-FC17-398F-B473-2AC9B4650081> /Users/USER/Library/Application Support/SIMBL/*/SafariStand.bundle/Contents/MacOS/SafariStand
I also had repeated Safari 6.0.4 crashes - particularly when entering accounts and passwords.
This solution worked!
The solution is to remove any SIMBL application, scripting addition, and application support folder.
Looks like SIMBL - a hack to MacOS X no longer is compatible with Safari and crashes it spectacularly.
I removed the following:
- /Users/USER/Library/Application Support/SIMBL/ --- I removed the whole folder.
- Harddrive/Applications/EasySIMBL --- I turned off then removed this application.
I restarted the Mac. Then Safari works perfectly again.
I had crashes too, though I cannot be sure that Safari was to blame. My whole computer froze, and I had to force a restart. I called Apple Support, and they had me reset the PRAM. And then reinstall the entire system
I was ready to take the Macbook Pro in to be serviced for a hardware problem when I saw this mention of SIMBL. I was using a software add-on called Safari Cookies, and that software does use SIMBL (whatever that is). I uninstalled Safari Cookies — though I will miss what it does.
My problems did begin with Safari 6.0.4, so I hope removing the add-on fixes things. But I have a question: should this kind of problem with the browser freeze the entire computer?
re: my post above regarding OSX crashes. Safari Cookies, and SIMBL. I sent an email the developer of Safari Cookies, whiches uses SIMBL. He answered within the minute, and he sent me an uninstaller for SIMBL. I am not sure this is the problem, but this kind of attenton form a developer is remarkable.
Their product, Safari Cookies, is an excellent product that selectivly prunes unwanted cookies when quiting the broweser.
Of course the my problem may have nothing to do with SIMBL -- my hardware could be dying. Nobody else metnoned the whole system hanging.
I am having the same issue with Safari but I am also having it happen with any/all of the core applications. The strange thing is that I don't have apps using SIMBL or at least I couldn't find any reference to it. I searched everywhere starting with the suggested:
- /Users/USER/Library/Application Support/SIMBL/
I looks like my issue is with any core app that accesses the web:
- App Store
However, it isn't an issue with my Internet... I downloaded Firefox on my other laptop, moved the dmg over the network to this one, and installed it. It works great and is what I am using to trouble shoot including this message board right now.
ps... Here is the error (part of it) in case it helps...
Process: WebProcess  Path: /System/Library/PrivateFrameworks/WebKit2.framework/WebProcess.app/Contents/MacO S/WebProcess Identifier: com.apple.WebProcess Version: 8536 (8536.30.1) Build Info: WebKit2-7536030001000000~9 Code Type: X86-64 (Native)
Parent Process: Safari 
User ID: 501 Date/Time: 2013-06-06 01:06:39.754 -0700 OS Version: Mac OS X 10.8.4 (12E55)
Report Version: 10
Interval Since Last Report: 11018 sec Crashes Since Last Report: 28
Per-App Interval Since Last Report: 57 sec
Per-App Crashes Since Last Report: 14
Anonymous UUID: 6901DB8F-3CEE-057B-AAB3-109483927FA8
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020
VM Regions Near 0x20:
__TEXT 000000010c55d000-000000010c55e000 [ 4K] r-x/rwx SM=COW /System/Library/PrivateFrameworks/WebKit2.framework/WebProcess.app/Contents/Mac OS/WebProcess
Application Specific Information:
Bundle controller class: