NEW 278801
REGRESSION (280449@main): [ macOS wk2 ] imported/w3c/web-platform-tests/navigation-api/navigation-methods/return-value/navigate-intercept-interrupted.html is a flaky crash
https://bugs.webkit.org/show_bug.cgi?id=278801
Summary REGRESSION (280449@main): [ macOS wk2 ] imported/w3c/web-platform-tests/navig...
Anfernee Viduya
Reported 2024-08-28 11:30:57 PDT
imported/w3c/web-platform-tests/navigation-api/navigation-methods/return-value/navigate-intercept-interrupted.html is a flaky crash HISTORY: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fnavigation-api%2Fnavigation-methods%2Freturn-value%2Fnavigate-intercept-interrupted.html&platform=ios&platform=mac LOG: This stack was produced locally and symbolicated as Bot did not produce a crash log. 0 WebKit 0x7ff9206683f9 WebKit::crashDueWebKitFrameworkVersionMismatch() + 5 1 WebKit 0x7ff920668223 WTF::Detail::CallableWrapper<WebKit::XPCServiceEventHandler(NSObject<OS_xpc_object>*)::'block-literal'::$_1, void>::call() + 487 2 JavaScriptCore 0x7ff838f26152 void WTF::dispatchWorkItem<WTF::Function<void ()>>(void*) + 18 REPRODUCIBILITY: I was able to reproduce this issue on ToT using command run-webkit-test imported/w3c/web-platform-tests/navigation-api/navigation-methods/return-value/navigate-intercept-interrupted.html --iterations=10 DESCRIPTION: On 280449@main changes were made around Navigation.
Attachments
Radar WebKit Bug Importer
Comment 1 2024-08-28 11:31:07 PDT
EWS
Comment 2 2024-08-28 12:05:19 PDT
Test gardening commit 282856@main (bcd349a2e3d6): <https://commits.webkit.org/282856@main> Reviewed commits have been landed. Closing PR #32843 and removing active labels.
Anfernee Viduya
Comment 3 2024-10-22 16:03:04 PDT
Thanks to rbuis@igalia.com for bringing up that this bug is no longer reproducible on ToT with said command even with a --force invocation. Also verified it is not a test leakage. On results history it is still flaky crashing. Im setting up machine thats also affected here to try and reproduce again.
Note You need to log in before you can comment on or make changes to this bug.