3 ms·
The error message that Safari is showing means that the web content process is crashing. This should leave logs in ~/Library/Logs/DiagnosticReports (easily view
by saagarjha 6y ago
The error message that Safari is showing means that the web content process is crashing. This should leave logs in ~/Library/Logs/DiagnosticReports (easily viewable in Console, under "Crash Reports"). Without those it's unlikely that anybody will be able to provide any further information as to what is happening here.
- owyn 6y agoThanks for this comment! I applied this security update yesterday and it updated Safari and I get the same reliable crashes on some web pages. The really annoying thing is after it crashes a couple of times it blanks out the whole page. Normally there's a small banner that says "this page crashed" sure, but now it is a full screen error message saying "this page crashed too many times", making the site entirely unusable. Every time it crashes in the same place and leaves this in the logs: Dyld Error Message: Symbol not found: __ZN6webrtc24setVideoDecoderCallbacksEPFPvRKNS_14SdpVideoFormatEEPFiS0_EPFiS0_jPKhmttEPFiS0_S0_E Referenced from: /System/Library/StagedFrameworks/Safari/WebKit.framework/Versions/A/WebKit Expected in: /System/Library/StagedFrameworks/Safari/WebKit.framework/Versions/A/../../../libwebrtc.dylib Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 dyld 0x000000011767f3ba __abort_with_payload + 10 1 dyld 0x000000011767ebac abort_with_payload_wrapper_internal + 82 2 dyld 0x000000011767ebde abort_with_payload + 9 3 dyld 0x000000011763ea9d dyld::halt(char const*) + 343 4 dyld 0x000000011763ebc7 dyld::fastBindLazySymbol(ImageLoader\*, unsigned long) + 167 5 libdyld.dylib 0x00007fff60f4f32e dyld_stub_binder + 282 6 ??? 0x0000000108649008 0 + 4435775496 7 com.apple.WebKit 0x00000001083c758d WebKit::LibWebRTCProvider::createEncoderFactory() + 27 8 com.apple.WebCore 0x000000010ae7bdc9 WebCore::LibWebRTCProvider::createPeerConnectionFactory(rtc::Thread*, rtc::Thread\*) + 153 (etc)
- kabob 6y agoowyn: Same here! Did some digging and noticed something that might help. Notice in the "Symbol not found" the WebKit is looking in the dylib for a big honkin' symbol with "_jPKhmttEPFiS0_" near the end. When I opened the libwebrtc.dylib file in TextEdit, I see a very similar big honkin' symbol, but it's missing "tt" near the end. So that part of the symbol reads, "_jPKhmEPFiS0_". Don't know who's to blame, the WebKit or dylib file, but these two parts of Safari appear to identify some "setVideoDecoderCallbacks" code by 2 different names, and that's causing this crash!
- owyn 6y agoSomeone found a fix for it and it worked for me. If you re-install the Safari package again, it resolves the issue. Looks like it was the "combo" update that broke safari by installing things in the wrong order, which probably is why only some people were affected. Also "why software is hard". [0] https://forums.macrumors.com/threads/safari-14-1-is-completely-unusable.2293717/?post=29848146#post-29848146 https://forums.macrumors.com/threads/safari-14-1-is-complete... [1] https://www.macupdate.com/app/mac/15675/apple-safari https://www.macupdate.com/app/mac/15675/apple-safari