NEW 260411
REGRESSION(267014@main?): [ macOS x86_64 Debug ] Consistent unhandled message assertion ipc/restrictedendpoints/test-only-ipc-allowed.html
https://bugs.webkit.org/show_bug.cgi?id=260411
Summary REGRESSION(267014@main?): [ macOS x86_64 Debug ] Consistent unhandled message...
Ben Schwartz
Reported 2023-08-18 15:23:03 PDT
Created attachment 467335 [details] Parsed/prettified crash log ipc/restrictedendpoints/test-only-ipc-allowed.html This test is constantly crashing on macOS (x86_64) debug builds of wk2. HISTORY: https://results.webkit.org/?suite=layout-tests&test=ipc%2Frestrictedendpoints%2Ftest-only-ipc-allowed.html CRASH LOG (parsed from JSON, sample): Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000bbadbeef Exception Codes: 0x0000000000000001, 0x00000000bbadbeef Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [58266] VM Region Info: 0xbbadbeef is not in any region. Bytes before following region: 1362338065 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 10ce16000-10ce1a000 [ 16K] r-x/r-x SM=COW ...U.Development Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 JavaScriptCore 0x15f047a8e WTFCrash + 14 (Assertions.cpp:327) 1 WebKit 0x1386d5d6c WebKit::RemoteAudioSessionProxy::didReceiveMessage(IPC::Connection&, IPC::Decoder&) + 860 (RemoteAudioSessionProxyMessageReceiver.cpp:65) 2 WebKit 0x138770514 WebKit::GPUConnectionToWebProcess::dispatchMessage(IPC::Connection&, IPC::Decoder&) + 852 (GPUConnectionToWebProcess.cpp:894) 3 WebKit 0x138674b10 WebKit::GPUConnectionToWebProcess::didReceiveMessage(IPC::Connection&, IPC::Decoder&) + 1984 (GPUConnectionToWebProcessMessageReceiver.cpp:128) CRASH LOG URL (raw JSON, parsed attached): https://build.webkit.org/results/Apple-Ventura-Debug-WK2-Tests/267014@main%20(2832)/ipc/restrictedendpoints/test-only-ipc-allowed-crash-log.txt REPRODUCIBILITY: I was unable to reproduce this issue on the reported platform using run-webkit-tests. I will do some more testing to attempt to reproduce the issue. REGRESSION: I believe the regression point is at 267014@main, as this is the first crash instance and appears to have changes directly related to the subject of this test.
Attachments
Parsed/prettified crash log (11.94 KB, text/plain)
2023-08-18 15:23 PDT, Ben Schwartz
no flags
Radar WebKit Bug Importer
Comment 1 2023-08-18 15:23:14 PDT
EWS
Comment 2 2023-08-18 16:33:14 PDT
Test gardening commit 267062@main (8b5bc663a8ee): <https://commits.webkit.org/267062@main> Reviewed commits have been landed. Closing PR #16850 and removing active labels.
Ben Schwartz
Comment 3 2023-08-21 11:22:31 PDT
REPRODUCIBILITY: I was able to reproduce this bug on macOS Ventura on the WK2 debug build at 267085@main by running the following command: rwt --clobber-old-results --debug --test-list=/path/to/run_tests.txt --force --verbose ipc/restrictedendpoints/no-test-only-ipc-expected-crash.html ipc/restrictedendpoints/test-only-ipc-allowed.html This problem only reproduces when ipc/restrictedendpoints/no-test-only-ipc-expected-crash.html is run before the reported test.
Ben Schwartz
Comment 4 2023-08-21 11:23:11 PDT
CORRECTION: Command was: rwt --clobber-old-results --debug --force --verbose ipc/restrictedendpoints/no-test-only-ipc-expected-crash.html ipc/restrictedendpoints/test-only-ipc-allowed.html
Note You need to log in before you can comment on or make changes to this bug.