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!

ClusterFuzz has detected this issue as fixed in range 575679:575681.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Sanitizer CHECK failure
Crash Address: 
Crash State:
  "(("unable to unmap" && 0)) != (0)" (0x0, 0x0)
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=483728:483739
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=575679:575681

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

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

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