RESOLVED DUPLICATE of bug 191108 191384
REGRESSION: STP 69: JSC crashes on ups.com navigation
https://bugs.webkit.org/show_bug.cgi?id=191384
Summary REGRESSION: STP 69: JSC crashes on ups.com navigation
Jon
Reported 2018-11-07 10:23:29 PST
Created attachment 354106 [details] Crash report. Attempting to navigate anywhere on ups.com causes a WebProcess crash from within JSC. Reloading without content blockers doesn't change anything. 10.14.1, iMac 18,3. Attached is the full report. Time Awake Since Boot: 210000 seconds Time Since Wake: 6700 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000002, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Trace/BPT trap: 5 Termination Reason: Namespace SIGNAL, Code 0x5 Terminating Process: exc handler [42428] Application Specific Information: Bundle controller class: BrowserBundleController Enabled App Extensions: com.agilebits.onepassword7.1PasswordSafariAppExtension (2BUA8C4S2C) (Version: 70201002 - Display Version: 7.2.1) 1Password com.khanov.BlockerMac.SafariExtension (6P9PN587KS) (Version: 70 - Display Version: 1.4.3) 1Blocker Button Enabled Content Blockers: com.khanov.BlockerMac.BlockerMacExtension (6P9PN587KS) (Version: 70 - Display Version: 1.4.3) 1Blocker Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.apple.JavaScriptCore 0x00000001eb261ac3 WTFCrashWithInfo(int, char const*, char const*, int) + 19 1 com.apple.JavaScriptCore 0x00000001eb9824be JSC::ExecState::bytecodeOffset() + 206 2 com.apple.JavaScriptCore 0x00000001eb98a81c JSC::StackVisitor::readNonInlinedFrame(JSC::ExecState*, JSC::CodeOrigin*) + 476 3 com.apple.JavaScriptCore 0x00000001eb983860 JSC::Interpreter::getStackTrace(JSC::JSCell*, WTF::Vector<JSC::StackFrame, 0ul, WTF::CrashOnOverflow, 16ul>&, unsigned long, unsigned long) + 144 4 com.apple.JavaScriptCore 0x00000001ebba5711 JSC::getStackTrace(JSC::ExecState*, JSC::VM&, JSC::JSObject*, bool) + 129 5 com.apple.JavaScriptCore 0x00000001ebba99d2 JSC::ErrorInstance::finishCreation(JSC::ExecState*, JSC::VM&, WTF::String const&, bool) + 274 6 com.apple.JavaScriptCore 0x00000001ebba5222 JSC::ErrorInstance::create(JSC::ExecState*, JSC::VM&, JSC::Structure*, WTF::String const&, WTF::String (*)(WTF::String const&, WTF::String const&, JSC::RuntimeType, JSC::ErrorInstance::SourceTextWhereErrorOccurred), JSC::RuntimeType, bool) + 162 7 com.apple.JavaScriptCore 0x00000001ebba52f7 JSC::createTypeError(JSC::ExecState*, WTF::String const&, WTF::String (*)(WTF::String const&, WTF::String const&, JSC::RuntimeType, JSC::ErrorInstance::SourceTextWhereErrorOccurred), JSC::RuntimeType) + 103 8 com.apple.JavaScriptCore 0x00000001ebbacd33 JSC::createError(JSC::ExecState*, JSC::JSValue, WTF::String const&, WTF::String (*)(WTF::String const&, WTF::String const&, JSC::RuntimeType, JSC::ErrorInstance::SourceTextWhereErrorOccurred)) + 243 9 com.apple.JavaScriptCore 0x00000001eb21edd8 JSC::createNotAFunctionError(JSC::ExecState*, JSC::JSValue) + 56 10 com.apple.JavaScriptCore 0x00000001eba70465 JSC::LLInt::setUpCall(JSC::ExecState*, JSC::CodeSpecializationKind, JSC::JSValue, JSC::LLIntCallLinkInfo*) + 453 11 com.apple.JavaScriptCore 0x00000001eb438694 llint_entry + 61857 12 com.apple.JavaScriptCore 0x00000001eb43862c llint_entry + 61753
Attachments
Crash report. (29.74 KB, application/zip)
2018-11-07 10:23 PST, Jon
no flags
Radar WebKit Bug Importer
Comment 1 2018-11-07 14:25:43 PST
Alexey Proskuryakov
Comment 2 2018-11-07 14:26:26 PST
Tadeu, is this something that you already fixed, such as bug 191254?
Tadeu Zagallo
Comment 3 2018-11-07 14:30:17 PST
(In reply to Alexey Proskuryakov from comment #2) > Tadeu, is this something that you already fixed, such as bug 191254? From looking at the trace, it looks like the issue fixed in https://bugs.webkit.org/show_bug.cgi?id=191108.
Alexey Proskuryakov
Comment 4 2018-11-07 14:31:18 PST
Marking as such. *** This bug has been marked as a duplicate of bug 191108 ***
Note You need to log in before you can comment on or make changes to this bug.