This issue is related to swift shader, hence assigning to @capn for more updates on it.

Thanks!

Timeouts are expected, and we can't reasonably do anything about them.

ClusterFuzz testcase 5463544305549312 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

ClusterFuzz has detected this issue as fixed in range 558165:558166.

Detailed report: https://clusterfuzz.com/testcase?key=5463544305549312

Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  swiftshader_vertex_routine_fuzzer
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=545018:545023
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=558165:558166

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5463544305549312

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.