3 ms·
owyn: 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'
by kabob 5y ago
owyn: 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 5y 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