278041 2024-08-13 13:30:49 -0700 [ Mac Debug WK2 ] workers/worker-to-worker.html is consistently crashing 2024-08-15 11:09:53 -0700 1 1 1 Unclassified WebKit WebAssembly WebKit Nightly Build Unspecified Unspecified RESOLVED CONFIGURATION CHANGED https://bugs.webkit.org/show_bug.cgi?id=278132 InRadar P2 Normal --- 1 jenner webkit-unassigned ap d_degazio keith_miller mark.lam webkit-bot-watchers-bugzilla webkit-bug-importer youennf oldest_to_newest 2052468 0 jenner 2024-08-13 13:30:49 -0700 workers/worker-to-worker.html is consistently crashing on WK2 macOS Ventura Debug and later. HISTORY: https://results.webkit.org/?suite=layout-tests&test=workers%2Fworker-to-worker.html CRASH URL: https://build.webkit.org/results/Apple-Sonoma-Debug-AppleSilicon-WK2-Tests/282173@main%20(3717)/workers/worker-to-worker-crash-log.txt CRASH STDERR: 1 0x12cae4af8 JSC::Wasm::OpcodeOrigin::OpcodeOrigin(JSC::Wasm::OpType, unsigned int, unsigned long) 2 0x12cac8afc JSC::Wasm::OpcodeOrigin::OpcodeOrigin(JSC::Wasm::OpType, unsigned int, unsigned long) 3 0x12caa2270 JSC::Wasm::OMGIRGenerator::origin() 4 0x12caa8158 JSC::Wasm::OMGIRGenerator::addTableFill(unsigned int, JSC::B3::Variable*, JSC::B3::Variable*, JSC::B3::Variable*) 5 0x12cb43adc JSC::Wasm::FunctionParser<JSC::Wasm::OMGIRGenerator>::parseExpression() 6 0x12cb34ed8 JSC::Wasm::FunctionParser<JSC::Wasm::OMGIRGenerator>::parseBody() 7 0x12cac4cec JSC::Wasm::FunctionParser<JSC::Wasm::OMGIRGenerator>::parse() 8 0x12cac8e84 JSC::Wasm::parseAndCompileOMG(JSC::Wasm::CompilationContext&, JSC::Wasm::OptimizingJITCallee&, JSC::Wasm::FunctionData const&, JSC::Wasm::TypeDefinition const&, WTF::Vector<JSC::Wasm::UnlinkedWasmToWasmCall, 0ul, WTF::CrashOnOverflow, 16ul, WTF::FastMalloc>&, JSC::Wasm::CalleeGroup&, JSC::Wasm::ModuleInformation const&, JSC::MemoryMode, JSC::Wasm::CompilationMode, unsigned int, std::__1::optional<bool>, unsigned int, JSC::Wasm::TierUpCount*) 9 0x12cb8c7dc JSC::Wasm::OMGPlan::work(JSC::Wasm::Plan::CompilationEffort) 10 0x12cc2a3f0 JSC::Wasm::Worklist::Thread::work() 11 0x12a5bb45c WTF::AutomaticThread::start(WTF::AbstractLocker const&)::$_0::operator()() const 12 0x12a5bb00c WTF::Detail::CallableWrapper<WTF::AutomaticThread::start(WTF::AbstractLocker const&)::$_0, void>::call() 13 0x12a5d7814 WTF::Function<void ()>::operator()() const 14 0x12a70d718 WTF::Thread::entryPoint(WTF::Thread::NewThreadContext*) 15 0x12a719f98 WTF::wtfThreadEntryPoint(void*) 16 0x19c48af94 _pthread_start 17 0x19c485d34 thread_start com.apple.WebKit.WebContent.Development terminated (pid 16806) for reason: crash LEAK: 1 WebPageProxy 2052469 1 webkit-bug-importer 2024-08-13 13:31:07 -0700 <rdar://problem/133784222> 2052471 2 ews-feeder 2024-08-13 13:39:51 -0700 Test gardening commit 282190@main (20bce1134f43): <https://commits.webkit.org/282190@main> Reviewed commits have been landed. Closing PR #32129 and removing active labels. 2052862 3 ap 2024-08-14 17:11:37 -0700 This test doesn't use WASM, so the issue must be caused by a preceding test that we should skip. 2053035 4 mark.lam 2024-08-15 09:33:28 -0700 According to https://results.webkit.org/?suite=layout-tests&test=workers%2Fworker-to-worker.html, the crashes have stopped manifesting. 2053042 5 ap 2024-08-15 10:07:38 -0700 Robert suspects that this was fixed by 282247@main. Still need to revert the gardening commit, of course. 2053045 6 mark.lam 2024-08-15 10:12:49 -0700 (In reply to Alexey Proskuryakov from comment #5) > Robert suspects that this was fixed by 282247@main. Still need to revert the > gardening commit, of course. 282247@main is Wasm specific. Since this test does not exercise Wasm at all, it cannot possibly be caused by 282247@main. The original crash trace may be erroneous and from a different test failing due to the bug that 282247@main fixed. 2053048 7 ews-feeder 2024-08-15 10:24:02 -0700 Test gardening commit 282295@main (d7a3f89ea3cd): <https://commits.webkit.org/282295@main> Reviewed commits have been landed. Closing PR #32248 and removing active labels. 2053061 8 ap 2024-08-15 11:09:53 -0700 As discussed in Slack, the stack trace is correct, and it is not uncommon that some async processing leaks from one test to another. It's usually a problem in itself that navigating away doesn't entirely stop all background WebKit code for it.