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

Thanks!

ClusterFuzz has detected this issue as fixed in range 552580:552581.

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

Fuzzer: attekett_surku_fuzzer
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Breakpoint
Crash Address: 0xffffbc8b222da080
Crash State:
  NULL
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=538997:539001
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=552580:552581

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

See https://github.com/google/clusterfuzz-tools 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 5906517015134208 is verified as fixed, so closing issue as verified.

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