Unable to find actual suspect through code search and also observing no CL's under regression range, hence adding appropriate label and requesting someone from dev team to look in to this issue.

Thanks!

Here is the change log:
https://chromium.googlesource.com/chromium/src/+log/1690f8c61b434d2a76ce5cc54fb92f1b9a302f99..7bc0d6eb583fb67cc550d0834aae5eaac2588123?pretty=fuller&n=10000

lushniov@, can you please look into this change (https://chromium.googlesource.com/chromium/src/+/bfc75c0a27fff772ed4d96ef40dfd6f127ee29fa) and see if it's related?

Thank you!

ClusterFuzz testcase 5314342862716928 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 600304:600305.

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

Fuzzer: libFuzzer_css_parser_proto_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  css_parser_proto_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=523878:523908
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=600304:600305

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

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.