RESOLVED DUPLICATE of bug 231684 230833
[ Catalina Debug wk1 EWS] performance-api/performance-observer-order.html is a flaky crash
https://bugs.webkit.org/show_bug.cgi?id=230833
Summary [ Catalina Debug wk1 EWS] performance-api/performance-observer-order.html is ...
Eric Hutchison
Reported 2021-09-27 08:08:58 PDT
performance-api/performance-observer-order.html is a flaky crash on Catalina Debug wk1 EWS. History: https://results.webkit.org/?suite=layout-tests&test=storage%2Fwebsql%2Fmultiple-transactions-on-different-handles.html Results: https://ews-build.s3-us-west-2.amazonaws.com/macOS-Catalina-Debug-WK1-Tests-EWS/r439333-16096-rerun/results.html "No crash log found for DumpRenderTree:30021." 05:14:55.250 21869 worker/5 worker/5 performance-api/performance-observer-order.html crashed, (no stderr) 05:14:55.251 21869 [50760/55734] performance-api/performance-observer-order.html failed unexpectedly (DumpRenderTree crashed [pid=22058]) 05:14:55.251 21869 worker/5 killing driver 05:14:55.256 21869 worker/5 performance-api/performance-observer-order.html failed: 05:14:55.256 21869 worker/5 DumpRenderTree crashed [pid=22058] I don't have a platform to attempt repro.
Attachments
Radar WebKit Bug Importer
Comment 1 2021-09-27 08:10:30 PDT
Eric Hutchison
Comment 2 2021-09-27 08:14:11 PDT
Simon Fraser (smfr)
Comment 3 2021-09-27 08:23:02 PDT
Wrong history link in the first comment.
Alexey Proskuryakov
Comment 4 2021-09-29 16:10:03 PDT
05:12:54.927 21869 worker/5 performance-api/performance-observer-no-document-leak.html passed 05:12:55.237 21869 worker/5 killed pid 22058 05:14:55.250 21869 worker/5 worker/5 performance-api/performance-observer-order.html crashed, (no stderr) 05:14:55.251 21869 worker/5 killing driver 05:14:55.256 21869 worker/5 performance-api/performance-observer-order.html failed: 05:14:55.256 21869 worker/5 DumpRenderTree crashed [pid=22058] Nothing about "no output" here.
Eric Hutchison
Comment 5 2021-11-03 13:00:37 PDT
*** This bug has been marked as a duplicate of bug 231684 ***
Note You need to log in before you can comment on or make changes to this bug.