Bug 226110

Summary: ASSERTION FAILED: !isCompilationThread() in ctiStub of JITThunks.cpp since r277850
Product: WebKit Reporter: Fujii Hironori <Hironori.Fujii>
Component: JavaScriptCoreAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal    
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on: 225998    
Bug Blocks:    
Attachments:
Description Flags
crash log (WinCairo WK1 Debug) none

Description Fujii Hironori 2021-05-21 13:48:46 PDT
ASSERTION FAILED: !isCompilationThread() in ctiStub of JITThunks.cpp since r277850

WinCairo-64-bit-WKL-Debug-Tests is crashing since r277850 (Bug 225998).

https://build.webkit.org/#/builders/32/builds/438

ASSERTION FAILED: !isCompilationThread()
..\..\Source\JavaScriptCore\jit/JITThunks.cpp(138) : ctiStub
1   00007FFE258213E9 WTFCrash
2   00007FFE10DF1F8D WTFCrashWithInfo
3   00007FFE11C97EA9 JSC::JITThunks::ctiStub
4   00007FFE123884DD JSC::VM::getCTIStub
5   00007FFE10F98EF8 JSC::CallLinkInfo::emitSlowPath
6   00007FFE11C0320D JSC::JIT::compileOpCallSlowCase<JSC::OpCall>
7   00007FFE11BF54DA JSC::JIT::emitSlow_op_call
8   00007FFE11BC94B3 JSC::JIT::privateCompileSlowCases
9   00007FFE11BCD387 JSC::JIT::compileAndLinkWithoutFinalizing
10  00007FFE11CA12AD JSC::JITWorklist::Plan::compileInThread
11  00007FFE11CA06E2 JSC::JITWorklist::Thread::work
12  00007FFE25827C11 WTF::AutomaticThread::start::<unnamed-tag>::operator()
13  00007FFE258278F7 WTF::Detail::CallableWrapper<`lambda at ..\..\Source\WTF\wtf\AutomaticThread.cpp:173:9',void>::call
14  00007FFE25833A14 WTF::Function<void ()>::operator()
15  00007FFE2589F92B WTF::Thread::entryPoint
16  00007FFE25963053 WTF::wtfThreadEntryPoint
17  00007FFE4E171BB2 configthreadlocale
18  00007FFE4ED77034 BaseThreadInitThunk
19  00007FFE50A62651 RtlUserThreadStart
Comment 1 Fujii Hironori 2021-05-21 13:49:41 PDT
Created attachment 429335 [details]
crash log (WinCairo WK1 Debug)
Comment 2 Fujii Hironori 2021-05-23 12:56:04 PDT
It seems fixed by r277882.

*** This bug has been marked as a duplicate of bug 226105 ***