Pretty sure this is the same as  issue 733058 , just the stach-trace changed. Please feel free to de-dupe into  issue 733058  if my suspicion holds.

This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

 Issue 733058  has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 45952:45953.

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

Fuzzer: inferno_js_fuzzer_c
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  0 != hash_ in hash-table.h
  Hash
  Hash
  
Sanitizer: address (ASAN)

Regressed: V8: 45909:45910
Fixed: V8: 45952:45953

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 5622943051939840 is verified as fixed, so closing issue.

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

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot