Unable to find actual suspect through code search and also from the provided CL under regression range, hence adding appropriate label and leaving it as untriaged for further updates.

Thanks!

Looks webrtc related.

Philip, could you take a look?

ClusterFuzz has detected this issue as fixed in range 563603:563819.

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

Fuzzer: libFuzzer_packet_buffer_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

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

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=491655:491671
Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=563603:563819

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

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.

ClusterFuzz testcase 6211450675396608 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.