Bug 275080

Summary:	REGRESSION (279647@main): [ MacOS iOS ] 2K TestIPC.ConnectionTest/ConnectionRunLoopTest.SendWithConvertedPromisedReply are consistent crashes
Product:	WebKit	Reporter:	Jay Stfleur <j_stfleur>
Component:	New Bugs	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED FIXED
Severity:	Normal	CC:	webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority:	P2	Keywords:	InRadar
Version:	WebKit Nightly Build
Hardware:	Unspecified
OS:	Unspecified

Jay Stfleur

Reported 2024-06-03 15:51:51 PDT

Description: TestIPC.ConnectionTest/ConnectionRunLoopTest.SendWithConvertedPromisedReply/ServerIsA TestIPC.ConnectionTest/ConnectionRunLoopTest.SendWithConvertedPromisedReply/ClientIsA Both tests are consistent crashes on Debug but flaky on release. These are new tests introduced by 279647@main Buildbot URL: https://build.webkit.org/#/builders/940/builds/1680 History: https://results.webkit.org/?suite=api-tests&suite=api-tests&test=TestIPC.ConnectionTest%2FConnectionRunLoopTest.SendWithConvertedPromisedReply%2FServerIsA&test=TestIPC.ConnectionTest%2FConnectionRunLoopTest.SendWithConvertedPromisedReply%2FClientIsA&recent=false Diff/Image Diff/Crash Log: ASSERTION FAILED: queue.isCurrent() /Volumes/Data/worker/Apple-iOS-17-Simulator-Debug-Build/build/WebKitBuild/Debug-iphonesimulator/usr/local/include/wtf/FunctionDispatcher.h(60) : void WTF::assertIsCurrent(const SerialFunctionDispatcher &) Child process terminated with signal 5: Trace/BPT trap

Attachments
Add attachment proposed patch, testcase, etc.

Radar WebKit Bug Importer

Comment 1 2024-06-03 15:52:17 PDT

Jay Stfleur

Comment 2 2024-06-03 16:08:59 PDT

Reproducibility: run-api-tests --debug -v TestIPC.ConnectionTest/ConnectionRunLoopTest.SendWithConvertedPromisedReply/ClientIsA --iterations 3

Alexey Proskuryakov

Comment 3 2024-06-04 09:42:12 PDT

EWS

Comment 4 2024-06-05 03:41:18 PDT

Committed 279734@main (22a4b2c1b41b): <https://commits.webkit.org/279734@main> Reviewed commits have been landed. Closing PR #29493 and removing active labels.

Note You need to log in before you can comment on or make changes to this bug.