Predator and CL did not provide any possible any possible suspects.
Using Code Search for the file, "handles.h" assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/v8/v8.git/+/ab56c223393444cb6e15a2863821170b9b09fd26

@ahaas -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

ClusterFuzz has detected this issue as fixed in range 478632:478686.

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

Fuzzer: afl_v8_wasm_code_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  (location_) != nullptr in handles.h
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=468010:468046
Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=478632:478686

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


See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.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 has detected this issue as fixed in range 478632:478686.

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

Fuzzer: afl_v8_wasm_code_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  (location_) != nullptr in handles.h
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=468010:468046
Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=478632:478686

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


See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.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 5646657120370688 is verified as fixed, so closing issue.

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