Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

OSX 10.10.4 Safari WebKit2 Quit Unexpectedly

I upgraded from 10.6.8 about 9 months ago and crash, crash, crash - not just safari; chrome and firefox would "Quit Unexpectedly" and either crash the browser or the page fails and it reloads.


So I did a "clean install" of 10.10.4 (14E46) thinking that something was wrong with the upgrade.


Going to 10.10.4 not only didn't stop the problem, it made it worse. A dozen or more times a day is not uncommon. After the rebuild I slowly brought over different programs. Anecdotally after adding SOPHOS the problem seemed to increase in frequency, but I can't prove this assertion.


Here's the Header. Only Thread 0 reports as crashed.


I reviewed other posts but am not seeing anything that looks helpful.


I can post the whole log but its VERY long.


Since my mac is fast becoming an expensive paperweight, I'd love to figure out what the heck is going on!


Thanks for your help.

===============================================================================


Process: com.apple.WebKit.WebContent [1057]

Path: /System/Library/Frameworks/WebKit.framework/Versions/A/XPCServices/com.apple.We bKit.WebContent.xpc/Contents/MacOS/com.apple.WebKit.WebContent

Identifier: com.apple.WebKit.WebContent

Version: 10600 (10600.7.12)

Build Info: WebKit2-7600007012000000~2

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Safari [223]

User ID: 501


Date/Time: 2015-07-27 23:27:26.075 -0700

OS Version: Mac OS X 10.10.4 (14E46)

Report Version: 11

Anonymous UUID: (blanked out for support case)


Sleep/Wake UUID: (blanked out for support case)


Time Awake Since Boot: 25000 seconds

Time Since Wake: 13000 seconds


Crashed Thread: 0 Dispatch queue: com.apple.main-thread


Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x00000000bbadbeef


VM Regions Near 0xbbadbeef:

-->

__TEXT 00000001021cd000-00000001021ce000 [ 4K] r-x/rwx SM=COW /System/Library/Frameworks/WebKit.framework/Versions/A/XPCServices/com.apple.We bKit.WebContent.xpc/Contents/MacOS/com.apple.WebKit.WebContent


Application Specific Information:

Bundle controller class:

BrowserBundleController


Process Model:

Multiple Web Processes



Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 com.apple.JavaScriptCore 0x00007fff8a9c55fe WTFCrash + 62

1 com.apple.JavaScriptCore 0x00007fff8a8fdab4 JSC::CodeBlock::finalizeUnconditionally() + 2036

2 com.apple.JavaScriptCore 0x00007fff8a7f4869 JSC::SlotVisitor::finalizeUnconditionalFinalizers() + 57

3 com.apple.JavaScriptCore 0x00007fff8ab21465 JSC::Heap::collect(JSC::HeapOperation) + 389

4 com.apple.JavaScriptCore 0x00007fff8aa16986 JSC::GCActivityCallback::doWork() + 134

5 com.apple.JavaScriptCore 0x00007fff8a7ea3ea JSC::HeapTimer::timerDidFire(__CFRunLoopTimer*, void*) + 170

6 com.apple.CoreFoundation 0x00007fff8c6802e4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20

7 com.apple.CoreFoundation 0x00007fff8c67ff73 __CFRunLoopDoTimer + 1059

8 com.apple.CoreFoundation 0x00007fff8c6f353d __CFRunLoopDoTimers + 301

9 com.apple.CoreFoundation 0x00007fff8c63b608 __CFRunLoopRun + 2024

10 com.apple.CoreFoundation 0x00007fff8c63abd8 CFRunLoopRunSpecific + 296

11 com.apple.HIToolbox 0x00007fff8eeaa56f RunCurrentEventLoopInMode + 235

12 com.apple.HIToolbox 0x00007fff8eeaa2ea ReceiveNextEventCommon + 431

13 com.apple.HIToolbox 0x00007fff8eeaa12b _BlockUntilNextEventMatchingListInModeWithFilter + 71

14 com.apple.AppKit 0x00007fff88fff8ab _DPSNextEvent + 978

15 com.apple.AppKit 0x00007fff88ffee58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346

16 com.apple.AppKit 0x00007fff88ff4af3 -[NSApplication run] + 594

17 com.apple.AppKit 0x00007fff88f71244 NSApplicationMain + 1832

18 libxpc.dylib 0x00007fff81c21958 _xpc_objc_main + 793

19 libxpc.dylib 0x00007fff81c23060 xpc_main + 490

20 com.apple.WebKit.WebContent 0x00000001021cdb40 0x1021cd000 + 2880

21 libdyld.dylib 0x00007fff84ffe5c9 start + 1

...

Thread 0 crashed with X86 Thread State (64-bit):

rax: 0x00000000bbadbeef rbx: 0x00000000d2dc7307 rcx: 0x0000000000000000 rdx: 0x00007fff7324e1f8

rdi: 0x0000000000000000 rsi: 0x0000150000001500 rbp: 0x00007fff5da30160 rsp: 0x00007fff5da30050

r8: 0x00007fff5da2fe40 r9: 0x00007fff7303a300 r10: 0x0000000000000000 r11: 0x0000000000000246

r12: 0x0000000115dbf808 r13: 0x0000000000000012 r14: 0x0000000119fdc6c0 r15: 0x0000000000000110

rip: 0x00007fff8a9c55fe rfl: 0x0000000000010206 cr2: 0x00000000bbadbeef


Logical CPU: 0

Error Code: 0x00000006

Trap Number: 14

iMac (21.5-inch Late 2009), OS X Yosemite (10.10.4)

Posted on Jul 30, 2015 11:59 PM

Reply
2 replies

Jul 31, 2015 7:01 AM in response to twhouse1

That kind of crash is usually, or perhaps always, caused by a hardware fault.

If your model has user-replaceable memory, and you've upgraded the memory modules, reinstall the original memory and see whether there's any improvement. Otherwise, remove half the memory and test; then switch and test the other half. Be careful not to touch the gold contacts. Clean them with a mild solvent such as rubbing alcohol. Aftermarket memory must exactly match the technical specifications for your model. Memory that is either slower or faster than specified may be incompatible.

Apple Diagnostics or the Apple Hardware Test, though generally unreliable, will sometimes detect a fault. A negative test can't be depended on. Run the extended version of the test, if applicable.

OSX 10.10.4 Safari WebKit2 Quit Unexpectedly

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.