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

Thanks!

ClusterFuzz has detected this issue as fixed in range 555680:555682.

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

Fuzzer: inferno_twister
Job Type: windows_asan_content_shell
Platform Id: windows

Crash Type: Fatal error
Crash Address: 
Crash State:
  NULL
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=539001:539005
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=555680:555682

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

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 4786642318262272 is verified as fixed, so closing issue as verified.

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