RESOLVED WORKSFORME 232412
[ iOS ] imported/blink/compositing/video/video-controls-layer-creation-squashing.html is a flaky GPUProcess crash/timeout
https://bugs.webkit.org/show_bug.cgi?id=232412
Summary [ iOS ] imported/blink/compositing/video/video-controls-layer-creation-squash...
ayumi_kojima
Reported 2021-10-27 17:25:03 PDT
imported/blink/compositing/video/video-controls-layer-creation-squashing.html Is a flaky crash and timeout on iOS 15. History: https://results.webkit.org/?suite=layout-tests&test=imported%2Fblink%2Fcompositing%2Fvideo%2Fvideo-controls-layer-creation-squashing.html Result page: https://build.webkit.org/results/Apple-iOS-15-Simulator-Release-WK2-Tests/r284930%20(331)/results.html Crash log: No crash log found for WebKitTestRunnerApp:74559. stdout: Content-Type: text/plain FAIL: Timed out waiting for notifyDone to be called #PID UNRESPONSIVE - WebKitTestRunnerApp (pid 74559) #EOF #EOF stderr: #EOF Failed to load 'about:blank', terminating process and trying again. com.apple.WebKit.WebContent.Development terminated (pid 84432) because the client requested #CRASHED - GPUProcess (pid 84408) Stderr: #EOF Failed to load 'about:blank', terminating process and trying again. com.apple.WebKit.WebContent.Development terminated (pid 84432) because the client requested #CRASHED - GPUProcess (pid 84408)
Attachments
Radar WebKit Bug Importer
Comment 1 2021-10-27 17:25:27 PDT
ayumi_kojima
Comment 2 2021-10-27 17:37:01 PDT
ayumi_kojima
Comment 3 2021-10-28 16:20:34 PDT
I was not able to reproduce the crash or timeout locally on iOS 15 sim using run-webkit-tests --ios-simulator --force --iterations 500 --exit-after-n-crashes-or-timeouts 1 imported/blink/compositing/video/video-controls-layer-creation-squashing.html. Tried --test-list as well, but I couldn't reproduce.
Alexey Proskuryakov
Comment 4 2022-04-25 16:28:29 PDT
This test continues to fail, crash, and time out periodically.
Ben Schwartz
Comment 5 2024-03-22 21:49:14 PDT
The last time this crashed or timed out was on iOS 16 on November 2, 2022. Can we consider this resolved?
Note You need to log in before you can comment on or make changes to this bug.